90 to 300 (intercontinental) | 20 to 100 (regional)
90 to 400 (intercontinental) | 20 to 500 | +| Jitter (peak-to-peak) | ms | 0 to 50 | 0 to 150 | 0 to 500 | +| Sequential packet loss | ms | Random loss only | 40 to 200 | 40 to 10'000 | +| Rate of sequential loss | s -1 | Random loss only | < 10 -3 | < 10 -1 | +| Random packet loss | % | 0 to 0.05 | 0 to 2 | 0 to 20 | +| Reordered packets | % | 0 to 0.001 | 0 to 0.01 | 0 to 0.1 | + +## 7.2 Impairment combination standard test cases + +The standard test cases of this IP network model have the following characteristics for each service test profile: + +- Well-managed network (Profile A) – a network with no over-committed links that employs QoS edge routing. The well-managed test cases include managed voice and video services. +- Partially managed network (Profile B) – a network that minimizes over-committed links and has one or more links without QoS edge routing. The partially managed test cases include a mixture of managed voice and video services, and unmanaged/best-effort data and over-the-top video services. +- Unmanaged network (Profile C) – an unmanaged network such as the Internet that includes over-committed links and has one or more links without QoS edge routing. The unmanaged test cases include unmanaged data and over-the-top video services. + +The specific core network parameters, interferers, and access network parameters for each test case were selected so that the simulation results align with the impairment level requirements of clause 7.1, with an adjustment to account for the fact that the simulations only cover the core-to-LAN topology. The interferers represent a realistic mix of typical traffic. The test cases span a range of impairment severities from mild to severe within each service test profile. + +The test cases are specified in Tables 7, 8 and 9. Each test case is labelled in Table E.1 as follows: + +- The first character is either D for DSL or G for GPON. The access rates and impairments chosen represent typical values in 2010. (The single core-only test case, lacking an access network portion, is labelled simply "Core."). +- The second character is one of the following: + - **w** for well-managed profile A, highlighted in green in Table 7. + - **p** for partially managed profile B, highlighted in yellow in Table 8. + - **u** for unmanaged profile C, highlighted in red in Table 9. + +The third character is an ordinal digit, where a higher value generally corresponds to a higher severity (more difficult) test case. + +For example, test case Dw5 uses DSL access in a well-managed network with impairment severity 5. Note that all simulations are for the core-to-LAN network topology of Figure 4. + +A given test case column uses the identical interfering streams and parameters between the DSL and GPON versions. Only the access technology parameters differ. + +The column "PCAP Avg BW" shows the long-term average bit rate of each pcap file after smoothing, but before scaling. The percentages shown for each pcap file under each test case are the time scale factors applied to the interferers by the packet generator. A higher percentage decreases the inter-packet time, which increases the effective bit rate of the interferer. + +**Table 7 – Well-managed service test profile A test cases** + +| Network Element | Impairment / Interferer | PCAP Avg BW (Mb/s) | Well Managed | | | | | | | | +|-----------------------------------------------|-------------------------------|-----------------------|--------------|--------|--------|--------|--------|--------|--------|--------| +| | | | w1 | w2 | w3 | w4 | w5 | w6 | w7 | w8 | +| Core | | | | | | | | | | | +| | Number of Switches | | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | +| | Total Core Link Delay (ms) | | 10 | 25 | 50 | 75 | 85 | 100 | 125 | 150 | +| | | | | | | | | | | | +| Access (pick one technology) | | | | | | | | | | | +| GPON | Access Rate Down (Mbit/s) | | 50 | 50 | 35 | 35 | 25 | 25 | 25 | 15 | +| | Access Rate Up (Mbit/s) | | 25 | 25 | 25 | 25 | 25 | 25 | 25 | 5 | +| | Residual BER | | 1.E-12 | 1.E-12 | 1.E-11 | 1.E-10 | 1.E-10 | 1.E-09 | 1.E-09 | 1.E-09 | +| DSL | Access Rate Down (Mbit/s) | | 33 | 33 | 33 | 22 | 16 | 16 | 16 | 10 | +| | Access Rate Up (Mbit/s) | | 3 | 3 | 3 | 2 | 1 | 1 | 1 | 1 | +| | Residual BER | | 1.E-08 | 1.E-08 | 1.E-08 | 1.E-08 | 1.E-07 | 1.E-07 | 1.E-07 | 1.E-07 | +| | | | | | | | | | | | +| Managed Bandwidth | | (QoS Voice=1 Video=2) | | | | | | | | | +| | IPTV HD Stream 1 - CBR (qty) | 8 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| | IPTV HD Stream 2 - VBR (qty) | 8 | | | 1 | | | | | | +| | IPTV SD Stream 1 - CBR (qty) | 2 | | 1 | | 1 | 1 | 1 | 1 | | +| | IPTV SD Stream 2 - VBR (qty) | 2 | | | | 1 | | 1 | 1 | | +| | VoIP/Fax (qty) | 0.064/0.064 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| | | | | | | | | | | | +| Residual Bandwidth (Internet Services) | | QoS = 7 | | | | | | | | | +| | Bandwidth and Delay Variation | | | | | | | | | | + +**Table 8 – Partially-managed service test profile B test cases** + +| Network Element | Impairment / Interferer | PCAP Avg BW (Mb/s) | Unmanaged | | | | | | | +|-------------------------------------|-------------------------------|-----------------------|----------------------------------------------------------------------|--------|--------|--------|--------|--------|--------| +| | | | u1 | u2 | u3 | u4 | u5 | u6 | u7 | +| Core | | | | | | | | | | +| | Number of Switches | | 3 | 4 | 5 | 8 | 10 | 12 | 15 | +| | Total Core Link Delay (ms) | | 10 | 25 | 50 | 75 | 100 | 200 | 250 | +| | | | | | | | | | | +| Access (pick one technology) | | | | | | | | | | +| GPON | Access Rate Down (Mbit/s) | | 35 | 35 | 25 | 15 | 5 | 15 | 5 | +| | Access Rate Up (Mbit/s) | | 35 | 15 | 25 | 5 | 2 | 5 | 2 | +| | Residual BER | | 1.E-12 | 1.E-12 | 1.E-11 | 1.E-09 | 1.E-09 | 1.E-09 | 1.E-09 | +| DSL | Access Rate Down (Mbit/s) | | 24 | 18 | 12 | 6 | 3 | 6 | 3 | +| | Access Rate Up (Mbit/s) | | 3 | 1.5 | 1.5 | 1 | 1 | 1 | 1 | +| | Residual BER | | 1.E-08 | 1.E-07 | 1.E-07 | 1.E-06 | 1.E-06 | 1.E-06 | 1.E-06 | +| | | | | | | | | | | +| Managed Bandwidth | | (QoS Voice=1 Video=2) | | | | | | | | +| | IPTV HD Stream 1 - CBR (qty) | 8 | There are no managed streams in the Unmanaged service test profile C | | | | | | | +| | IPTV HD Stream 2 - VBR (qty) | 8 | | | | | | | | +| | IPTV SD Stream 1 - CBR (qty) | 2 | | | | | | | | +| | IPTV SD Stream 2 - VBR (qty) | 2 | | | | | | | | +| | VoIP/Fax (qty) | 0.064/0.064 | | | | | | | | +| | | | | | | | | | | +| Residual Bandwidth | | QoS = 7 | | | | | | | | +| | Bandwidth and Delay Variation | | | | | | | | | + +**Table 9 – Unmanaged service test profile C cases** + +| Network Element | Impairment / Interferer | PCAP Avg BW (Mb/s) | Partially Managed | | | | | | +|-----------------------------------------------|-------------------------------|------------------------------|-------------------|--------|--------|--------|--------|--------| +| | | | p1 | p2 | p3 | p4 | p5 | p6 | +| Core | | | | | | | | | +| | Number of Switches | | 3 | 4 | 5 | 8 | 10 | 12 | +| | Total Core Link Delay (ms) | | 10 | 25 | 50 | 75 | 100 | 200 | +| Access (pick one technology) | | | | | | | | | +| GPON | Access Rate Down (Mbit/s) | | 35 | 35 | 25 | 15 | 5 | 15 | +| | Access Rate Up (Mbit/s) | | 35 | 15 | 25 | 5 | 2 | 5 | +| | Residual BER | | 1.E-12 | 1.E-12 | 1.E-11 | 1.E-09 | 1.E-09 | 1.E-09 | +| DSL | Access Rate Down (Mbit/s) | | 24 | 18 | 12 | 6 | 3 | 6 | +| | Access Rate Up (Mbit/s) | | 3 | 1.5 | 1.5 | 1 | 1 | 1 | +| | Residual BER | | 1.E-08 | 1.E-07 | 1.E-07 | 1.E-06 | 1.E-06 | 1.E-06 | +| Managed Bandwidth | | (QoS Voice=1 Video=2) | | | | | | | +| | IPTV HD Stream 1 - CBR (qty) | 8 | | | | | | | +| | IPTV HD Stream 2 - VBR (qty) | 8 | | | | | | | +| | IPTV SD Stream 1 - CBR (qty) | 2 | 1 | 1 | 1 | 1 | 0 | 1 | +| | IPTV SD Stream 2 - VBR (qty) | 2 | 1 | 1 | 1 | 1 | 1 | 1 | +| | VoIP/Fax (qty) | 0.064/0.064 | 1 | 1 | 1 | 1 | 1 | 1 | +| Residual Bandwidth (Internet Services) | | QoS = 7 | | | | | | | +| | Bandwidth and Delay Variation | | | | | | | | + +Figure 12 shows the aggregate bit rate over time for the DSL well-managed profile. Test profile A has the following characteristics: + + + +Figure 12: Managed bandwidth for DSL well-managed profile A both directions. The figure contains two stacked line graphs. The top graph, titled 'Managed Bandwidth Well Managed', shows a stable aggregate bit rate around 0.024 Mbit/s over 600 seconds. The bottom graph shows individual stream bit rates over the same period, with multiple lines fluctuating between 0 and 20 Mbit/s. The legend indicates eight data series: Dw1-t, Dw2-t, Dw3-t, Dw4-t, Dw5-t, Dw6-t, Dw7-t, and Dw8-t. + +**Figure 12 – Managed bandwidth for DSL well-managed profile A both directions** + +Figure 13 shows the aggregate bit rate over time for the DSL partially-managed profile. Test profile B has the following characteristics: + + + +Figure 13: Managed bandwidth for DSL partially-managed profile B both directions. The figure consists of two vertically stacked line graphs sharing a common x-axis representing time in seconds from 0 to 600. The top graph, titled 'Managed Bandwidth' and 'Fully Managed', shows a dense, noisy signal fluctuating between approximately 0.022 and 0.024 Mbps. The bottom graph shows two data series: a purple line representing one direction's bandwidth usage, which fluctuates between 0 and 4 Mbps, and a blue line representing the other direction's usage, which fluctuates between 0 and 2 Mbps. A legend at the bottom indicates the data series are Dp14, Dp24, Dp34, Dp44, Dp54, and Dp64. + +**Figure 13 – Managed bandwidth for DSL partially-managed profile B both directions** + +NOTE – The Un-managed profile has no managed traffic, therefore there are no managed traffic plots. All of the bandwidth is available for iPerf. + +# 8 Using the network model + +The network model described by this Recommendation is implemented as a software simulator. For each test case, the simulator models the network behaviour while carrying a mixture of user datagram protocol (UDP) and TCP traffic. The UDP packets are taken from pcap files that represent real world managed services, such as IPTV or VoIP. The TCP packets are generated by an iPerf client and server that run within the simulator. The priority levels assigned to the UDP packets varies according to the specific test case. For all test cases, the priority level assigned to the TCP stream is best effort. + +For the UDP flows, the simulator records the latency for each packet, or if the packet is discarded during the simulation, the simulator records that it was dropped. These results are saved in an output file and can be used directly in an inline network impairment emulator. + +For the TCP stream, the simulator records the packets to a pcap file. At the conclusion of the simulation, the saved pcap file is analysed to determine the time-varying capacity that it used. This is taken to represent the network capacity available for best effort services. For each 200-millisecond time slot in the pcap file, the packet delay (latency), bandwidth and loss, are measured and these results are saved to an output file. + +The output files for all the test cases are published in electronic form as Annex H of this Recommendation. The output files can then be used in an in-line network impairment emulator to evaluate the performance of a service carried over a best-effort TCP stream. + +Alternatively, the simulator can also be used as a stand-alone evaluation platform to determine the residual best-effort capacity of a network under customized test cases that are different from the predefined test cases in this Recommendation. For this, a user may select different network parameters (link speeds, bit error rates or priorities), or select different interference traffic patterns. If desired, the simulator output for such customized test cases may also be used in an in-line network impairment emulator. + +## 8.1 Using an in-line network impairment emulator + +Figure 14 illustrates user defined test streams being replayed through the residual unmanaged bandwidth of a network model. Figure 15 shows an example of a lab test set-up where data is played between a device under test A (data source) and device under test B (data sink) through an in-line network impairment emulator. + + + +Figure 14: Example Lab environment diagram. A red box labeled 'ns-3' contains a 'Network model' cloud. Inside the box, 'Managed bandwidth' (Table 3) is shown between two groups of applications: 'IPTV 1, IPTV 2, IPTV 3, IPTV 4, VoIP' (Defined by network model) and 'IPTV 1, IPTV 2, IPTV 3, IPTV 4, VoIP'. Below the cloud, 'Residual Un-managed' (Table 4) is shown between 'Internet services' and 'User defined test stream(s)' (Examples: peer-to-peer, HTTP, OTT, RTP/UDP, Un-managed VoIP). Streams 1, 2, 3, and N are shown entering and exiting the box. A yellow arrow points down to 'Annex F Table 2: Network characteristic files'. Reference G.1050(16)\_F14 is at the bottom right. + +**Figure 14 – Test user applications with network characteristic files** + + + +Figure 15: Hardware emulator test set-up diagram. A flow diagram showing 'Device under test A (data source)' connected to 'Network emulator (network characteristic files)' which is connected to 'Device under test B (data sink)'. 'Test stream(s)' are indicated between each device and the emulator. Reference G.1050(16)\_F15 is at the bottom right. + +**Figure 15 – Hardware emulator test set-up** + +The in-line network impairment emulator could be used as follows: + +- network characteristic files can be replayed by a network emulator to test user defined stream(s) or applications; +- select a test case that includes a technology similar to the test stream; +- configure the emulator with the standard .out file from Annex F Table 2 for the selected test case: + - Table 3 – Managed bandwidth – replay delay and drop; + - Table 4 – Residual bandwidth – replay bandwidth and delay. +- run the test stream(s) through the emulator, and evaluate the effect of the network impairments on the stream. + +## 8.2 Using the simulator to create custom test cases + +Modifications to existing test cases can be made as follows: + +- Select a standard test case as a starting point. See Annex G which provides a summary of all the test cases. This can be used as a roadmap to select the test case of interest. +- Replace or change settings in the parameter file to correspond to a desired test scenario. For example, link bit rates, error rates and latencies can be changed, as well as the number of core switches, or competing impairment streams. See clause A.9. +- Run the simulation, which results in a .out file, and optionally pcap captures for analysis. +- Evaluate performance using the simulator results. +- Optionally run the results on an in-line network impairment emulator. + +## 8.3 Hardware emulator considerations + +For a specified test case, the simulation produces bandwidth, delay and loss characteristics that can be used in a real-time emulator. The emulator accepts a packet stream under test, and plays out the same stream with impairments that match the corresponding simulation. + +The simulator creates .out files to represent the delay and loss experienced by each packet in a stream. These .out files can be used directly to control packet delay and loss in a real-time inline impairment emulator. + +In cases where the packet stream in the simulator is bursty, the delay and loss values in the .out file are non-uniform in time. Two methods to handle this situation are described in the following paragraphs. An impairment emulator shall provide Method 1 and may provide Method 2. + +Method 1: Resample the delay and loss values in the .out file so that they are uniformly sampled in time, and apply these in the inline impairment emulator using the resampled rate. For example, if the test stream is bursty with an average packet rate of 1000 packets per second, the .out file may be resampled using a 1 ms resample rate, and the resulting impairments could then be applied at a 1 ms update rate. This approach ensures that the resulting test always lasts the same amount of time, but some samples may apply to more than one packet, and other samples may not be applied to any packets, depending on the arrival time of packets at the inline impairment emulator. + +Method 2: Apply the delay and loss values from the .out files on a packet-by-packet basis. Each line in the .out file is applied to one packet without regard to the time value in the first column. This approach ensures that each delay and loss value is applied exactly once, but the test duration will vary inversely with the rate of packets applied to the inline impairment emulator. In other words, a higher packet rate applied to the emulator will consume the .out file samples more quickly, and thus the test finishes sooner. + +If a long duration test is required to last for more than the 10-minute length of the .out files, the files should be looped. + +An impairment emulator shall shape the stream under test to account for the "self-interference" effect by traffic shaping using the token bucket method. Packets that arrive close together in time contend for the available bandwidth in the emulated network. The amount of shaping depends on the effective bandwidth available to the stream under test in the given test case. This available capacity is the rate of the access link (the lowest-rate link in the network) less the sum of the rates of the interfering streams at QoS priority the same or higher than the stream under test. + +The test cases described in this Recommendation cover primarily CORE-TO-LAN configurations, and this is well suited for emulation of IPTV service and newer over-the-top streaming video services. Test cases for LAN-TO-LAN configurations shall be constructed by concatenating two CORE-TO-LAN test cases. For example, a LAN-TO-LAN test case could be constructed by running Dw1 in series with Gp3. Such a test case is called Dw1-Gp3. The delay and loss values for a LAN-TO-LAN test case are calculated by first performing Method 1 on the individual test cases so that they have a common sample rate and then summing the delay values and logically OR-ing the loss values for the resulting individual test cases. The bandwidth limitation is calculated as the minimum of the effective bandwidth (EB) for the individual test cases. + +$$\begin{aligned}\text{Delay}_{\text{Dw1-Gp2}} &= \text{Delay}_{\text{Dw1}} + \text{Delay}_{\text{Gp2}} \\ \text{Loss}_{\text{Dw1-Gp2}} &= \text{Loss}_{\text{Dw1}} \text{ "or" } \text{Loss}_{\text{Gp2}} \\ \text{BW}_{\text{Dw1-Gp2}} &= \text{Min}[\text{EB}_{\text{Dw1}}, \text{EB}_{\text{Gp2}}]\end{aligned}$$ + +## **8.4 Advanced uses of the network model** + +User-defined test cases: the user can define custom test cases by any of these methods: + +- replace any of the standard interferer pcap files; +- change the traffic mix; +- change network conditions: number of switches, bit error ratio, access technology parameters, etc. + +Network load generation: the output pcap files can be used as the basis of synthetic or dummy loads to inject onto networks to simulate different traffic mixes. + +# Annex A + +## Description of simulator + +(This annex forms an integral part of this Recommendation.) + +## A.1 Simulator overview + +The ITU-T G.1050-2016 impairment model is implemented with the ns-3 network simulator. ns-3 is a discrete-event network simulator for Internet systems. It is an open-source project written mainly in the C++ language using object oriented techniques and is licensed under the GNU Public License (v2). + +ns-3 is available to the public for research, development and use. The ns-3 project is hosted at the website [www.nsnam.org](http://www.nsnam.org), where source code, documentation and project announcements can be found. There are several email discussion forums that allow project members to communicate with each other and to publicly announce events such as new releases and upcoming conferences. + +ns-3 contains models of network elements, such as routers and communication links, as well as many popular network protocols such as TCP/IP. Events in the simulation consist mainly of packet arrivals and departures from the different network elements, but other types of events are also possible. + +An important reason for choosing ns-3 as the basis for the ITU-T G.1050-2016 model is that it contains a working TCP/IP network protocol stack. Attempts to add TCP/IP to the previous revision of the ITU-T G.1050 model proved difficult. Furthermore, ns-3 is able to run actual network code in the DCE virtual environment, which ensures the realism of the simulation. Specifically, the simulations use the Linux 2.6.36 network stack, but the DCE simulation environment will support other network stacks for future extensibility. + +The ITU-T G.1050-2016 impairment model is built on top of the base ns-3 code and has two main parts: patches and additions. The patches modify existing parts of ns-3 to extend functionality or fix minor errors. During the ITU-T G.1050 build process, the patches are applied to the base ns-3 code. Some or all of these patches may be incorporated in a future release of the base ns-3 code. The additions are new files that add features or functionality beyond what is available in the base ns-3 code. During the ITU-T G.1050 build process, these additional files are overlaid onto the base ns-3 directory structure and compiled with it. ns-3 release 3.24.1 was used as the basis for the simulations described in this Recommendation. + +The Core-to-LAN network topology described in clause 6.2 has been implemented in ns-3, and during simulations various traffic streams are transferred over this topology. The base traffic load on the model consists of various managed streams such as IPTV and VoIP. The residual capacity of the network beyond the base load is available for unmanaged streams, such as *Over-the-top* (OTT) video. + +The managed traffic streams in this model are represented by real-world packet captures contained in PCAP files. These managed streams are played into the model by reading the PCAP file, injecting the packets into the network from a simulated source node and addressing them to the simulated destination node. These packets form the background load carried by the Core-to-LAN topology. + +The unmanaged streams in the model are represented by TCP sessions between a simulated server and a simulated client. The server and client run a program called iPerf. iPerf sends data from the client to the server using a TCP session, and it sends data as fast as allowed by TCP. The packets carrying the iPerf session are given *best effort* priority. The iPerf session does a good job of measuring network capacity available to TCP-based best-effort services while competing with other managed services such as IPTV and VoIP. + +As the simulation runs, the iPerf packets are captured into PCAP files at the client and server nodes within the simulation. After the simulation finishes, the PCAP files are analysed to determine how the network capacity (or bandwidth) and packet delay vary over time during the simulation. The average bandwidth and delay are calculated once every 200 milliseconds and recorded in a file that can then be used to test other TCP-based best-effort services, for example with a network impairment emulator. + +As mentioned earlier, ns-3 is able to directly execute actual software for network protocols and applications. This is called direct code execution (DCE) and is a virtual execution environment for real-world network code. A simulated network node in ns-3 can run a virtualized instance of an actual TCP/IP network stack implementation, such as running the actual Linux kernel code for TCP/IP. A simulated network node can also run a virtualized instance of a network application, such as running the actual code for iPerf. Using DCE is better than running a separately implemented model because it uses the same source code of real systems, and has the same functionality. However, using DCE also slows down the overall simulation. + +For ITU-T G.1050-2016, the iPerf program and the supporting Linux kernel TCP/IP stack running on the client and server nodes are implemented as DCE virtual environments. The iPerf instances are compiled from publicly available iPerf version 2.0.5 source code. The Linux kernel source code on the client and server nodes is Linux version 2.6.36. Because of this, various TCP congestion control algorithms that exist in that version of Linux (e.g., reno, bic, cubic) can be selected and run. For this Recommendation, the cubic congestion control algorithm is used. Because TCP is not used on the other nodes of the simulated Core-to-LAN network and because using DCE slows down the simulation, the remaining network nodes use the regular ns-3 protocol models. The reason for this is to improve the runtime of the simulation. + +## A.2 Directory structure + +| | | +|----------------------------------------|-----------------------------------------------------| +| ./ | top level directory | +| analysis/ | directory of scripts for post analysis | +| dce/ | contains ns-3 and dce source code | +| ns-3.24.1-base.diff | contains ITU-T G.1050 patches to ns-3 | +| overlay/ | contains ITU-T G.1050 overlay code | +| setenv.sh | script to set environment variables | +| setup.sh | script that calls download, patch, overlay & build | +| download.sh | script to download ns-3 source code | +| patch.sh | script to apply ITU-T G.1050 patches to ns-3 | +| overlay.sh | script to overlay ITU-T G.1050 files to ns-3 | +| build.sh | script to build the modified ITU-T G.1050 simulator | +| rebuild.sh | script to rebuild the simulator | +| dce/source/ns-3-dce/myscripts/core2lan | contains ITU-T G.1050 core2lan model | +| dce/source/ns-3-dce/tc | contains ITU-T G.1050 test case files | +| dce/source/ns-3-dce/pcap | contains ITU-T G.1050 PCAP input files | +| dce/source/ns-3-dce/out | contains ITU-T G.1050 output files | + +## A.3 Building the simulator + +The source code for the simulation is written in the C++ language and has been tested in Ubuntu 14.04. + +The following is a list of Linux packages that are required in order to build and run the simulator: + +``` +build-essential, pkg-config, subversion, wireshark, flex, bison, gnuplot, tcl, tcl-dev, +libboost-dev, libboost-doc, libboost-all-dev, python-pygccxml, python-pygraphviz, mercurial, +python-pygoocanvas, bzip2, cmake, cvs, git, unrar, p7zip-full, autoconf, python, qt4, qt4-qmake, +qt4-dev-tools, libpcap-dev, libc6-dev, libc6-dbg, mercurial, libdb-dev, aptitude, libssl-dev +``` + +To build the simulator, first run the script `setenv.sh` to set the necessary environment variables. + +``` +$ source ./setenv.sh +``` + +Then, run the script `setup.sh` + +``` +$ ./setup.sh +``` + +This script has four phases: + +- 1) Downloads the base ns-3 simulator code (ns-3.24.1); +- 2) Applies the ITU-T G.1050-2016 patches that are part of this annex; +- 3) Adds the ITU-T G.1050-2016 overlay files; +- 4) Builds the modified simulator. + +It should be noted that the `setup.sh` script performs a full download and build, and if it runs successfully, no other commands are needed to prepare the simulator. + +## A.4 Download phase + +The following shows a simplified version of the messages that are printed during the download phase of the set-up. The download phase is based on a script published on the nsnam.org website for getting started with DCE. + +``` +$ ./setup.sh ++ source ./setenv.sh ++ hg clone http://code.nsnam.org/bake bake +requesting all changes +adding changesets +adding manifests +adding file changes +added 331 changesets with 787 changes to 63 files +updating to branch default +45 files updated, 0 files merged, 0 files removed, 0 files unresolved ++ mkdir dce ++ cd dce ++ bake.py configure -e dce-linux-1.4 ++ bake.py download -vvv +>> Download pybindgen-0.17.0.876 - OK +>> Search g++ - OK +>> Search qt4 - OK +>> Download bash - OK +>> Search python-dev - OK +>> Search pygraphviz - OK +>> Search pygoocanvas - OK +>> Search libpcap-dev - OK +>> Search libexpat-dev - OK +>> Download iperf - OK +>> Search libdb-dev - OK +>> Search bison - OK +>> Search flex - OK +>> Search libssl-dev - OK +>> Download net-next-sim-2.6.36 - OK +>> Download wget - OK +>> Download thttpd - OK +>> Download elf-loader - OK +>> Download netanim-3.105 - OK +>> Download ccnx - OK +>> Download iproute-2.6.38-fix-01 - OK +>> Download ns-3.24.1 - OK +>> Download dce-meta-1.4 - OK +>> Download dce-linux-1.4 - OK +``` + +## A.5 Patch phase to apply ITU-T G.1050-2016 patches + +Once all of the base files for ns-3 have been downloaded, some of the files are patched using the "patch" utility. The patches that are applied are maintained in a file called ns-3.24.1-base.diffs. The patches are organized in three groups according to the part of the base code that is patched. + +The first group of files that are patched belong to the core of the NS3 simulator. + +``` +source/ns-3.24.1/src/internet/model/global-router-interface.cc +source/ns-3.24.1/src/internet/model/global-router-interface.h +source/ns-3.24.1/src/network/utils/pcap-file.cc +source/ns-3.24.1/src/network/utils/pcap-file.h +source/ns-3.24.1/src/network/utils/pcap-file-wrapper.cc +source/ns-3.24.1/src/network/utils/pcap-file-wrapper.h +source/ns-3.24.1/src/network/helper/trace-helper.h +source/ns-3.24.1/src/internet/helper/ipv4-routing-helper.cc +``` + +- The patch to the global-router-interface code allows Ethernet switches to be connected together within a single layer 2 network. +- The patch to the pcap-file code extends the capabilities of the existing code to support nanosecond resolution time stamps, reading from PCAP files, rewinding PCAP files and fixes an error in the declaration of the magic number for nanosecond timestamp PCAP files. +- The patch to trace-helper fixes an error in the default value of arguments that control the default capture length of packets to PCAP files. + +The second group of files that are patched belong to the Linux kernel code that is run within the DCE environment of NS3. + +``` +source/net-next-sim-2.6.36/net/core/sock.c +source/net-next-sim-2.6.36/net/socket.c +source/net-next-sim-2.6.36/net/ipv4/ip_input.c +``` + +- The patch to the ip\_input.c code fixes a problem that occurs in ns-3 simulations in which some nodes use the Linux TCP/IP stack while other nodes use the native ns-3 TCP/IP stack. The problem occurs because the default behavior for Linux is to discard packets that have an incorrect IP header checksum, but the default behaviour of ns-3 is for these checksums to be disabled. Because calculating checksums is time consuming and slows down the simulation, instead of enabling checksum calculation in ns-3, the patch to ip\_input.h allows the Linux TCP/IP stack to recognize and process packets containing IP checksums that are set to zero (instead of discarding them). This behaviour is modelled upon the existing and well-known behaviour for receiving UDP packets with UDP checksums that are zero. + +The following shows a simplified version of the messages printed during the patch phase of the setup: + +``` ++ patch --verbose -p1 +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -c -r ns-3.24.1.ORIG/source/ns-3.24.1/src/internet/model/global-router-interface.cc +|*** ns-3.24.1.ORIG/source/ns-3.24.1/src/internet/model/global-router-interface.cc +|--- ns-3.24.1.TTA/source/ns-3.24.1/src/internet/model/global-router-interface.cc +----- +patching file source/ns-3.24.1/src/internet/model/global-router-interface.cc +Using Plan A... +Hunk #1 succeeded at 1242. +Hunk #2 succeeded at 1256. +Hunk #3 succeeded at 1289. +Hunk #4 succeeded at 1331. +Hunk #5 succeeded at 1355. +Hunk #6 succeeded at 1406. +Hunk #7 succeeded at 1419. +Hunk #8 succeeded at 1460. +Hunk #9 succeeded at 1485. +Hunk #10 succeeded at 1744. +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +``` + +``` + +----- +|diff -c -r ns-3.24.1.ORIG/source/ns-3.24.1/src/internet/model/global-router-interface.h +|*** ns-3.24.1.ORIG/source/ns-3.24.1/src/internet/model/global-router-interface.h +|--- ns-3.24.1.TTA/source/ns-3.24.1/src/internet/model/global-router-interface.h +----- +patching file source/ns-3.24.1/src/internet/model/global-router-interface.h +Using Plan A... +Hunk #1 succeeded at 769 (offset 1 line). +Hunk #2 succeeded at 783 (offset 1 line). +Hunk #3 succeeded at 848 (offset 1 line). +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -c -r ns-3.24.1.ORIG/source/ns-3.24.1/src/network/utils/drop-tail-queue.cc +|*** ns-3.24.1.ORIG/source/ns-3.24.1/src/network/utils/drop-tail-queue.cc +|--- ns-3.24.1.TTA/source/ns-3.24.1/src/network/utils/drop-tail-queue.cc +----- +patching file source/ns-3.24.1/src/network/utils/drop-tail-queue.cc +Using Plan A... +Hunk #1 succeeded at 35. +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -cr ns-3.24.1.ORIG/source/ns-3.24.1/src/network/helper/trace-helper.h +|*** ns-3.24.1.ORIG/source/ns-3.24.1/src/network/helper/trace-helper.h +|--- ns-3.24.1.TTA/source/ns-3.24.1/src/network/helper/trace-helper.h +----- +patching file source/ns-3.24.1/src/network/helper/trace-helper.h +Using Plan A... +Hunk #1 succeeded at 100 with fuzz 1 (offset 19 lines). +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -c ns-3.24.1.ORIG/source/ns-3.24.1/src/network/utils/pcap-file.cc +|*** ns-3.24.1.ORIG/source/ns-3.24.1/src/network/utils/pcap-file.cc +|--- ns-3.24.1.TTA/source/ns-3.24.1/src/network/utils/pcap-file.cc +----- +patching file source/ns-3.24.1/src/network/utils/pcap-file.cc +Using Plan A... +Hunk #1 succeeded at 40. +Hunk #2 succeeded at 48 (offset -1 lines). +Hunk #3 succeeded at 85 (offset -1 lines). +Hunk #4 succeeded at 161 (offset -1 lines). +Hunk #5 succeeded at 307 (offset -1 lines). +Hunk #6 succeeded at 331 (offset -1 lines). +Hunk #7 succeeded at 346 (offset -1 lines). +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -c ns-3.24.1.ORIG/source/ns-3.24.1/src/network/utils/pcap-file.h +|*** ns-3.24.1.ORIG/source/ns-3.24.1/src/network/utils/pcap-file.h +|--- ns-3.24.1.TTA/source/ns-3.24.1/src/network/utils/pcap-file.h +----- +patching file source/ns-3.24.1/src/network/utils/pcap-file.h +Using Plan A... +Hunk #1 succeeded at 116. +Hunk #2 succeeded at 172. +Hunk #3 succeeded at 199. +Hunk #4 succeeded at 366. +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -c ns-3.24.1.ORIG/source/ns-3.24.1/src/network/utils/pcap-file-wrapper.cc +|*** ns-3.24.1.ORIG/source/ns-3.24.1/src/network/utils/pcap-file-wrapper.cc +|--- ns-3.24.1.TTA/source/ns-3.24.1/src/network/utils/pcap-file-wrapper.cc +----- +patching file source/ns-3.24.1/src/network/utils/pcap-file-wrapper.cc +Using Plan A... +Hunk #1 succeeded at 17. +Hunk #2 succeeded at 40. +Hunk #3 succeeded at 58. +Hunk #4 succeeded at 110. + +``` + +``` + +Hunk #5 succeeded at 124. +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -c ns-3.24.1.ORIG/source/ns-3.24.1/src/network/utils/pcap-file-wrapper.h +|*** ns-3.24.1.ORIG/source/ns-3.24.1/src/network/utils/pcap-file-wrapper.h +|--- ns-3.24.1.TTA/source/ns-3.24.1/src/network/utils/pcap-file-wrapper.h +----- +patching file source/ns-3.24.1/src/network/utils/pcap-file-wrapper.h +Using Plan A... +Hunk #1 succeeded at 48. +Hunk #2 succeeded at 107. +Hunk #3 succeeded at 144. +Hunk #4 succeeded at 230. +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -cr ns-3.18.ORIG/source/net-next-sim-2.6.36/arch/sim/sim-socket.c +|*** ns-3.18.ORIG/source/net-next-sim-2.6.36/arch/sim/sim-socket.c +|--- ns-3.18.TTA/source/net-next-sim-2.6.36/arch/sim/sim-socket.c +----- +patching file source/net-next-sim-2.6.36/arch/sim/sim-socket.c +Using Plan A... +Hunk #1 succeeded at 174 (offset 13 lines). +Hunk #2 succeeded at 193 (offset 13 lines). +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -cr ns-3.18.ORIG/source/net-next-sim-2.6.36/net/core/sock.c +|*** ns-3.18.ORIG/source/net-next-sim-2.6.36/net/core/sock.c +|--- ns-3.18.TTA/source/net-next-sim-2.6.36/net/core/sock.c +----- +patching file source/net-next-sim-2.6.36/net/core/sock.c +Using Plan A... +Hunk #1 succeeded at 486. +Hunk #2 succeeded at 533. +Hunk #3 succeeded at 546. +Hunk #4 succeeded at 568. +Hunk #5 succeeded at 596. +Hunk #6 succeeded at 782. +Hunk #7 succeeded at 817. +Hunk #8 succeeded at 1311. +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -cr ns-3.18.ORIG/source/net-next-sim-2.6.36/net/socket.c +|*** ns-3.18.ORIG/source/net-next-sim-2.6.36/net/socket.c +|--- ns-3.18.TTA/source/net-next-sim-2.6.36/net/socket.c +----- +patching file source/net-next-sim-2.6.36/net/socket.c +Using Plan A... +Hunk #1 succeeded at 1756. +Hunk #2 succeeded at 1790. +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -cr ns-3.18.ORIG/source/net-next-sim-2.6.36/net/ipv4/ip_input.c +|*** ns-3.18.ORIG/source/net-next-sim-2.6.36/net/ipv4/ip_input.c +|--- ns-3.18.TTA/source/net-next-sim-2.6.36/net/ipv4/ip_input.c +----- +patching file source/net-next-sim-2.6.36/net/ipv4/ip_input.c +Using Plan A... +Hunk #1 succeeded at 415. +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -cr ns-3.24.1.ORIG/source/ns-3-dce/helper/linux-stack-helper.cc +|*** ns-3.24.1.ORIG/source/ns-3-dce/helper/linux-stack-helper.cc +|--- ns-3.24.1.TTA/source/ns-3-dce/helper/linux-stack-helper.cc +----- +patching file source/ns-3-dce/helper/linux-stack-helper.cc +Using Plan A... + +``` + +``` + +Hunk #1 succeeded at 64. +Hunk #2 succeeded at 117. +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -cr ns-3.24.1.ORIG/source/ns-3-dce/model/dce-fd.cc +|*** ns-3.24.1.ORIG/source/ns-3-dce/model/dce-fd.cc +|--- ns-3.24.1.TTA/source/ns-3-dce/model/dce-fd.cc +----- +patching file source/ns-3-dce/model/dce-fd.cc +Using Plan A... +Hunk #1 succeeded at 524 (offset 2 lines). +Hunk #2 succeeded at 535 (offset 2 lines). +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -cr ns-3.24.1.ORIG/source/ns-3-dce/model/unix-socket-fd.cc +|*** ns-3.24.1.ORIG/source/ns-3-dce/model/unix-socket-fd.cc +|--- ns-3.24.1.TTA/source/ns-3-dce/model/unix-socket-fd.cc +----- +patching file source/ns-3-dce/model/unix-socket-fd.cc +Using Plan A... +Hunk #1 succeeded at 245. +Hunk #2 succeeded at 303. +Hunk #3 succeeded at 318. +Hunk #4 succeeded at 484. +Hunk #5 succeeded at 555. +Hunk #6 succeeded at 574. +Hmm... The next patch looks like a new-style context diff to me... +The text leading up to this was: +----- +|diff -cr ns-3.24.1.ORIG/source/ns-3.24.1/src/internet/helper/ipv4-routing-helper.cc +|*** ns-3.24.1.ORIG/source/ns-3.24.1/src/internet/helper/ipv4-routing-helper.cc +|--- ns-3.24.1.TTA/source/ns-3.24.1/src/internet/helper/ipv4-routing-helper.cc +----- +patching file source/ns-3.24.1/src/internet/helper/ipv4-routing-helper.cc +Using Plan A... +Hunk #1 succeeded at 66. +done + +``` + +## A.6 Overlay phase – adding new code to the ITU-T G.1050-2016 simulator + +During the overlay phase, soft links are created to mirror the content of the files within the ./overlay directory tree into the ns-3 source code. This allows new files and modules to be added without modifying the existing distribution, while also allowing the overlay files to be maintained separately. + +The following is a list of the overlay files and a brief explanation of what each does. + +``` + +overlay/source/ns-3.24.1/src/tia921/model/asymmetric-link-channel.cc +overlay/source/ns-3.24.1/src/tia921/model/asymmetric-link-channel.h +overlay/source/ns-3.24.1/src/tia921/model/asymmetric-link-net-device.cc +overlay/source/ns-3.24.1/src/tia921/model/asymmetric-link-net-device.h +overlay/source/ns-3.24.1/src/tia921/helper/asymmetric-link-helper.cc +overlay/source/ns-3.24.1/src/tia921/helper/asymmetric-link-helper.h + +``` + +The asymmetric-link source code implements an asymmetric communication channel similar to typical access link such as the remote access (RACC) or local Access (LACC) channel in the CORE2LAN model. It has configurable speed, latency and bit error rate for each direction of transmission. + +``` + +overlay/source/ns-3.24.1/src/tia921/model/idxeth-channel.cc +overlay/source/ns-3.24.1/src/tia921/model/idxeth-channel.h +overlay/source/ns-3.24.1/src/tia921/model/idxeth-net-device.cc +overlay/source/ns-3.24.1/src/tia921/model/idxeth-net-device.h +overlay/source/ns-3.24.1/src/tia921/helper/idxeth-helper.cc +overlay/source/ns-3.24.1/src/tia921/helper/idxeth-helper.h + +``` + +The idxeth source code implements a full-duplex Ethernet communication model. ns-3 does not have a model for a full duplex Ethernet link. Therefore, this model is required. It has configurable speed and latency. It also implements packet transmission in a way that more accurately reflects the physical + +coding sublayer of the Ethernet protocol, in particular with regard to the required inter-frame gap and also generates transmission events in an order that allows future expansion to model cut-through switching. + +``` +overlay/source/ns-3.24.1/src/tia921/model/ethernet-priority-queue.cc +overlay/source/ns-3.24.1/src/tia921/model/ethernet-priority-queue.h +``` + +The Ethernet priority queue code implements priority queuing similar to what is used as part of the virtual LAN tag. + +``` +overlay/source/ns-3.24.1/src/tia921/model/pcap-packet-receiver.cc +overlay/source/ns-3.24.1/src/tia921/model/pcap-packet-receiver.h +overlay/source/ns-3.24.1/src/tia921/model/pcap-packet-sender.cc +overlay/source/ns-3.24.1/src/tia921/model/pcap-packet-sender.h +overlay/source/ns-3.24.1/src/tia921/helper/pcap-sendrecv-helper.cc +overlay/source/ns-3.24.1/src/tia921/helper/pcap-sendrecv-helper.h +``` + +The PCAP packet sender and receiver files implement objects to send and receive packets through an ns-3 simulation by reading from and writing to PCAP files. + +``` +overlay/source/ns-3.24.1/src/tia921/helper/switch-helper.cc +overlay/source/ns-3.24.1/src/tia921/helper/switch-helper.h +``` + +The switch helper code implements a subclass of the existing BridgeHelper class that has the additional convenience method for installing the L2 forwarding behaviour on a switch. + +``` +overlay/source/ns-3.24.1/src/tia921/model/prio-tag.cc +overlay/source/ns-3.24.1/src/tia921/model/prio-tag.h +overlay/source/ns-3.24.1/src/tia921/model/seq-ts-tag.cc +overlay/source/ns-3.24.1/src/tia921/model/seq-ts-tag.h +``` + +The priority tag and sequence timestamp tag code implement priority tags that are used by the Ethernet priority queue, and sequence-timestamp tags that are used by the PCAP sender and receivers. + +``` +overlay/source/ns-3-dce/myscripts/core2lan/core2lan.cc +overlay/source/ns-3-dce/myscripts/core2lan/setup-pcap.cc +overlay/source/ns-3-dce/myscripts/core2lan/setup-pcap.h +overlay/source/ns-3-dce/myscripts/core2lan/sim-param.cc +overlay/source/ns-3-dce/myscripts/core2lan/sim-param.h +``` + +The CORE2LAN code, along with the setup-pcap helper, and sim-param helper implement the top level of the simulation model. + +The process of overlaying is simply one of creating many soft links. The following is an excerpt of the first few lines that are printed during the overlay phase. + +``` ++ OVERLAYDIR=../overlay ++ xargs mkdir -p ++ grep -v '[.]svn' ++ cd ../overlay ++ find source -type d ++ read FILEPATH ++ grep -v '[.]svn' ++ cd ../overlay ++ find source -type f +++ dirname source/ns-3.24.1/src/tia921/helper/dash-server-helper.h ++ DIRNAME=source/ns-3.24.1/src/tia921/helper +++ sed -e 's:[^/]\+:...:g' +++ echo source/ns-3.24.1/src/tia921/helper ++ LINKPATH=../../../../../../overlay/source/ns-3.24.1/src/tia921/helper/dash-server-helper.h ++ ln -s -f ../../../../../../../../overlay/source/ns-3.24.1/src/tia921/helper/dash-server-helper.h +source/ns-3.24.1/src/tia921/helper +[...] ++ LINKPATH=../../../../../../overlay/source/ns-3-dce/run_core2lan.sh ++ ln -s -f ../../../../../../../../overlay/source/ns-3-dce/run_core2lan.sh source/ns-3-dce ++ read FILEPATH ++ ln -s myscripts/core2lan/tc source/ns-3-dce/tc ++ ln -s myscripts/core2lan/pcap source/ns-3-dce/pcap +``` + +## A.7 Build phase + +During the build phase, the source code for the modified base simulator and the ITU-T G.1050-2016 additional files are compiled. + +``` +>> Building iperf - OK +>> Building net-next-sim-2.6.36 - OK +>> Building wget - OK +>> Building pybindgen-0.17.0.876 - OK +>> Building thttpd - OK +>> Building bash - OK +>> Building ccnx - OK +>> Building iproute-2.6.38-fix-01 - OK +>> Building elf-loader - OK +>> Building netanim-3.105 - OK +>> Building ns-3.24.1 - OK +>> Building dce-linux-1.4 - OK +``` + +## A.8 The CORE2LAN model + +After the setup.sh script is run and the simulator is compiled, a number of new directories are created. The important ones are under ./dce/source: + +| | | +|-----------------------------------------|----------------------------------| +| ./dce/source/iperf | The iPerf TCP performance tester | +| ./dce/source/net-next-sim-2.6.36 | The Linux operating system | +| ./dce/source/ns-3.24.1 | The ns-3 source code | +| ./dce/source/ns-3-dce | The DCE add-on for ns-3 | + +Because the ITU-T G.1050 model uses DCE, it is added to the DCE subdirectory. Within the DCE directory, there are several new files and subdirectories: + +| | | +|----------------------------|-----------------------------| +| myscripts/core2lan/ | The core2lan test case | +| pcap@ | The PCAP input files | +| run_core2lan.sh@ | A script to run a test case | +| tcl@ | The test case files | +| out/ | The simulator output files | + +## A.9 Simulator input data + +Input to the simulator is in the form of PCAP files. These files are driven into the simulation as specified by the timestamps in PCAP files. The payload of the PCAP files, if present, is carried along with the packets in the simulation and placed in the output files. The simulation parameter settings can adjust the timing of the packets driven into the simulation, for example, to speed up or slow down the playback, or to smooth out unintended burstiness. A full list of the adjustable parameters for the PCAP packet generator is given below. + +The parameters for running the simulation are given in a TCL file. The advantage of using TCL as a parameter file format is that it is a well-known file format, and it is extensible so that users can further customize the behaviour of the simulation to suit their particular needs. It also allows reuse of the test case parameter files from the previous revision of this Recommendation. An example of how this helps is that it gives a convenient way to comment out portions of code and to print messages to the screen for information or debugging. + +At the very top of a parameter file, the user must include the common support routines from the file tc/common.tcl. + +``` +source "tc/common.tcl" +``` + +The first section of the parameter file consists of variable settings using the TCL "set" command. It is no different from setting a normal variable in TCL, except that the names of the variables are specific to the simulator. The example below sets the simulation length to 10 minutes (600 seconds) + +``` +# - - - - - +# Simulation length +# - - - - - +set SimLengthSeconds [expr 10*60] +``` + +In most test cases, the above line is commented out so that a default simulation length from common.tcl can control the duration of the simulation. + +Note also in this example that a TCL expression computes the number of seconds in ten minutes. While it is also possible to specify 600 seconds, using an expression in this way helps to make clear what is intended (10 minutes) and also serves as an example of how to use TCL expressions in the parameter file. + +Next, set the access and core network parameters (this example is from test case Dp4): + +``` +# - - - - - +# Network Parameters +# - - - - - +Set_Access_Params dsl_p4_u4 +Set_Core_Params p4_u4 +``` + +The first line above sets parameters for the access network. The second line above sets parameters for the core network. The arguments to these two procedures is a text string that refers to a pre-defined combination of parameters that are given in common.tcl. Custom test cases can be created by setting the individual simulator control variables at this level. + +Table A.1 shows the names of the predefined access parameters, and the corresponding access parameters: + +Table A.1 – Predefined access parameters + +| Tech Param Name | Node | SpeedDn | SpeedUp | BER_Fwd | BER_Rev | LatcyDn | LatcyUp | +|-----------------|------|----------|----------|----------|----------|----------|----------| +| dsl_w1 | RACC | 3.30E+07 | 3.00E+06 | 1.00E-08 | 1.00E-08 | 1.00E-03 | 1.00E-03 | +| dsl_w2 | RACC | 3.30E+07 | 3.00E+06 | 1.00E-08 | 1.00E-08 | 1.00E-03 | 1.00E-03 | +| dsl_w3 | RACC | 3.30E+07 | 3.00E+06 | 1.00E-08 | 1.00E-08 | 1.00E-03 | 1.00E-03 | +| dsl_w4 | RACC | 2.20E+07 | 2.00E+06 | 1.00E-08 | 1.00E-08 | 1.00E-03 | 1.00E-03 | +| dsl_w5 | RACC | 1.60E+07 | 1.00E+06 | 1.00E-07 | 1.00E-07 | 1.00E-03 | 1.00E-03 | +| dsl_w6 | RACC | 1.60E+07 | 1.00E+06 | 1.00E-07 | 1.00E-07 | 1.00E-03 | 1.00E-03 | +| dsl_w7 | RACC | 1.60E+07 | 1.00E+06 | 1.00E-07 | 1.00E-07 | 1.00E-03 | 1.00E-03 | +| dsl_w8 | RACC | 1.00E+07 | 1.00E+06 | 1.00E-07 | 1.00E-07 | 1.00E-03 | 1.00E-03 | +| pon_w1 | RACC | 5.00E+07 | 2.50E+07 | 1.00E-12 | 1.00E-12 | 1.00E-03 | 1.00E-03 | +| pon_w2 | RACC | 5.00E+07 | 2.50E+07 | 1.00E-12 | 1.00E-12 | 1.00E-03 | 1.00E-03 | +| pon_w3 | RACC | 3.50E+07 | 2.50E+07 | 1.00E-11 | 1.00E-11 | 1.00E-03 | 1.00E-03 | +| pon_w4 | RACC | 3.50E+07 | 2.50E+07 | 1.00E-11 | 1.00E-11 | 1.00E-03 | 1.00E-03 | +| pon_w5 | RACC | 2.50E+07 | 2.50E+07 | 1.00E-10 | 1.00E-10 | 1.00E-03 | 1.00E-03 | +| pon_w6 | RACC | 2.50E+07 | 2.50E+07 | 1.00E-09 | 1.00E-09 | 1.00E-03 | 1.00E-03 | +| pon_w7 | RACC | 2.50E+07 | 2.50E+07 | 1.00E-09 | 1.00E-09 | 1.00E-03 | 1.00E-03 | +| pon_w8 | RACC | 1.50E+07 | 5.00E+06 | 1.00E-09 | 1.00E-09 | 1.00E-03 | 1.00E-03 | +| pon_p1_u1 | RACC | 3.50E+07 | 3.50E+07 | 1.00E-12 | 1.00E-12 | 1.00E-03 | 1.00E-03 | +| pon_p2_u2 | RACC | 3.50E+07 | 1.50E+07 | 1.00E-12 | 1.00E-12 | 1.00E-03 | 1.00E-03 | +| pon_p3_u3 | RACC | 2.50E+07 | 2.50E+07 | 1.00E-11 | 1.00E-11 | 1.00E-03 | 1.00E-03 | +| pon_p4_u4 | RACC | 1.50E+07 | 5.00E+06 | 1.00E-09 | 1.00E-09 | 1.00E-03 | 1.00E-03 | +| pon_p5_u5 | RACC | 5.00E+06 | 2.00E+06 | 1.00E-09 | 1.00E-09 | 1.00E-03 | 1.00E-03 | +| pon_p6_u6 | RACC | 1.50E+07 | 5.00E+06 | 1.00E-09 | 1.00E-09 | 1.00E-03 | 1.00E-03 | +| pon_p7_u7 | RACC | 5.00E+06 | 2.00E+06 | 1.00E-09 | 1.00E-09 | 1.00E-03 | 1.00E-03 | +| dsl_p1_u1 | RACC | 2.40E+07 | 3.00E+06 | 1.00E-08 | 1.00E-08 | 1.00E-03 | 1.00E-03 | +| dsl_p2_u2 | RACC | 1.80E+07 | 1.50E+06 | 1.00E-07 | 1.00E-07 | 1.00E-03 | 1.00E-03 | +| dsl_p3_u3 | RACC | 1.20E+07 | 1.50E+06 | 1.00E-06 | 1.00E-06 | 1.00E-03 | 1.00E-03 | +| dsl_p4_u4 | RACC | 6.00E+06 | 1.00E+06 | 1.00E-06 | 1.00E-06 | 1.00E-03 | 1.00E-03 | +| dsl_p5_u5 | RACC | 3.00E+06 | 1.00E+06 | 1.00E-06 | 1.00E-06 | 1.00E-03 | 1.00E-03 | +| dsl_p6_u6 | RACC | 6.00E+06 | 1.00E+06 | 1.00E-06 | 1.00E-06 | 1.00E-03 | 1.00E-03 | +| dsl_p7_u7 | RACC | 3.00E+06 | 1.00E+06 | 1.00E-06 | 1.00E-06 | 1.00E-03 | 1.00E-03 | + +Table A.2 shows the names of the predefined access parameters, and the corresponding access parameters: + +**Table A.2 – Predefined core parameters** + +| Name | NumCoreSW | Latency | Speed | +|-------|-----------|----------|----------| +| w1 | 3 | 10.0E-3 | 1.00E+09 | +| w2 | 4 | 25.0E-3 | 1.00E+09 | +| w3 | 5 | 50.0E-3 | 1.00E+09 | +| w4 | 6 | 75.0E-3 | 1.00E+09 | +| w5 | 7 | 85.0E-3 | 1.00E+09 | +| w6 | 8 | 100.0E-3 | 1.00E+09 | +| w7 | 9 | 125.0E-3 | 1.00E+09 | +| w8 | 10 | 150.0E-3 | 1.00E+09 | +| p1_u1 | 3 | 10.0E-3 | 1.00E+09 | +| p2_u2 | 4 | 25.0E-3 | 1.00E+09 | +| p3_u3 | 5 | 50.0E-3 | 1.00E+09 | +| p4_u4 | 8 | 75.0E-3 | 1.00E+09 | +| p5_u5 | 10 | 100.0E-3 | 1.00E+09 | +| p6_u6 | 12 | 200.0E-3 | 1.00E+09 | +| p7_u7 | 15 | 250.0E-3 | 1.00E+09 | + +The next section of the parameter file specifies the input and output packet streams. PacketGenerators read input PCAP files and drive them into the simulation. PacketMonitors receive packets from elements within the simulation and save them in PCAP format, and also save delay and packet loss information. + +An example of this for test case Dp4-t is shown below: + +``` +# ===== +# Managed Bandwidth PCAP Stream Generators and Monitors +# +# Name File Start BW PPM Rand Prio Repeat PIR PBS +# ----- +PCAP_Generator PktGenPCAPFwdI4 SD_cbr 5.0 0.260 0.0 0.0 2 -1 ;# 2.0Mb/s +PCAP_Generator PktGenPCAPFwdI5 SD_vbr 5.0 0.361 0.0 0.0 2 -1 ;# 2.0Mb/s +PCAP_Generator PktGenPCAPFwdI1 voip_g729_fwd 2.0 1.0 0.0 0.0 1 -1 +PCAP_Generator PktGenPCAPRevI1 voip_g729_rev 2.0 1.0 0.0 0.0 1 -1 + +PCAP_Monitor PktMonPCAPFwdI1 VoIP1_Fwd +PCAP_Monitor PktMonPCAPFwdI4 SDTV1_Down +PCAP_Monitor PktMonPCAPFwdI5 SDTV2_Down +PCAP_Monitor PktMonPCAPRevI1 VoIP1_Rev +``` + +The parameters for the input PCAP generators are specified in the columns as shown above. The meanings of the columns are described briefly below. + +- **Instance name (Name)** – the instance name of the generator. This depends on the specific top level simulation file. +- **Filename (file)** – the file name of the input PCAP file. Assumes that the PCAP file is in the ./pcap subdirectory and has a .pcap suffix so neither of these needs to be specified in the parameter file. +- **Start delay (start)** – the relative delay, in seconds, before starting the generator. +- **Bandwidth scale factor (BW)** – a scale factor that divides the relative timestamps in the PCAP file. A value of 1.0 makes no change to the timing of the packets. A value of 2.0 causes the packets to be transmitted twice as fast by dividing the timestamps in the PCAP file by 2.0. + +- **PPM offset (PPM)** – this is similar to the bandwidth scale factor, but is expressed in units of parts per million. A value of 0 ppm makes no change to the rate at which packets are generated. A value of 100 ppm reduces the timestamps in the PCAP file by 100 ppm, which causes the file to be transmitted 100 ppm faster than the nominal rate. +- **Randomness (Rand)** – this is a value from 0.0 to 1.0 that adds a percentage of randomness to the inter-packet times. A value of 0.5 represents 50% randomness for inter-packet timing. For example, if the time between two consecutive packets in the PCAP file is 1 millisecond, and the randomness is 0.5, then the actual time between those two consecutive packets could be in the range 500 microsecond to 1.5 millisecond. +- **Priority (Prio)** – this is the assigned priority of the packets. +- **Repeat count (Repeat)** – this is the number of times to repeat the PCAP file. A value of 0 or 1 means to play the file once, a value of two or more will play the file that many times, and a value of –1 will repeat the file forever. +- **Shaper PIR (PIR) and shaper PBS (PBS)** – these parameters control a shaper that is built into the PacketGeneratorPCAP object. The PIR is the peak information rate and is expressed in bits per second, so the value 10E6 represents 10 million bits per second. The PBS is the peak burst size and is expressed in bits. Normally the PIR should be set safely above (e.g., 2.5x) the bit rate of a VBR video stream, unless the goal is to smooth out microbursts. + +The PacketMonitor outputs PCAP files and ".out" files. There are only two parameters for the PCAP monitor command: + +- **Instance name** – the instance name of the monitor. This depends on the specific top level simulation file. +- **File name** – the base name of the output files. The output files will be placed into the same directory as the parameter file and will have suffixes .pcap and .out. + +Note that if a PCAP\_Monitor line is commented out or not present, the output files will not be written. This is helpful in situations where only a subset of the output files is needed so that disk space can be saved. + +The simulation provides the following global variables for use by the TCL code in the parameter file: + +- **\$paramfile** – this is the name of the parameter file; +- **\$paramdir** – this is the directory name of the parameter file; +- **\$outdir** – this is the output directory name, and is set based on \$paramfile in common.tcl. + +## A.10 Running a simulation case with a convenience script + +To run one test case, there is a convenience script called run\_core2lan.ss. An example of running the test case "Du6-t" is shown below: + +``` +./run_core2lan.sh Du6-t --pcapUp=1 --pcapDown=1 --iperfDown --verbose=2 --capLen=70 +``` + +## A.11 Simulator output + +All output files for test case *tcname* are placed in the *./out/tcname* subdirectory. By placing the output results for each test case in their own directory, it is easier to keep them organized. By placing the outputs in a separate directory from the input parameter settings, the output results can be easily cleaned up, and it is easier to manage the parameter files. + +As described in the section above on the parameter file, it is not necessary to save output for all of the streams being tested. This can be helpful in conserving disk space, as the output files can be quite large. + +#### A.11.1 Output for UDP flows + +For the managed UDP streams, such as IPTV and VoIP, the simulator output is in the form of PCAP files and ".out" files. The PCAP files record the managed stream output packets along with their timestamps. Comparisons of input PCAP and output PCAP files can be performed to determine the effect of the impairment on, for example, video quality. + +The ".out" output files contain delay and packet loss information (in ASCII CSV format) about the simulation result. This information is also implicitly contained in the PCAP file, but because it is not possible to directly indicate packet delay or loss in a PCAP file, the ".out" files are helpful for post analysis. For example, because the ".out" files are in CSV format, they can be read into a spreadsheet program for analysis. + +The columns contained in the .out file reflect the time the packet was transmitted into the network, the delay experienced by the packet and a flag indicating whether the packet was dropped by the network. Time is represented as the number of seconds since the beginning of the simulation and has nanosecond resolution (nine digits after the decimal point). Packet delay is represented by milliseconds and has nanosecond resolution (6 digits after the decimal point). Drop is a Boolean flag represented by a 0 or a 1 (1 means a packet was dropped, 0 means successful reception). + +#### A.11.2 Output for TCP flows + +The pcap files for the TCP flows generated by the iPerf client and server are analysed after the simulations finish. There is a pcap file captured at the server port, and a pcap file captured at the client port. That way, every packet at the server can be matched with the corresponding packet at the client so that one-way network delay can be calculated for each packet in each direction. + +The post analysis is run by the top level script "analysis/postall." It processes the pcap files for each test case with a helper script called "postz." The postz script uses the "tstat" "tshark" and "bw" utilities to extract information from the pcap files. The result of the postz script is four files: + +- iperf-[up/down]-client.csv; +- iperf-[up/down]-server.csv; +- bw-[up/down].csv; +- del-[up/down].csv. + +NOTE – for upstream iPerf, select "up" and for downstream iPerf, select "down". + +After postz is run on all of the test cases, "postall" then uses the "merge.pl" script to create an "R" language script to create summary plots where results for all test cases are merged onto a single page. + +## A.12 Plotting results + +The results are plotted by the top level script "analysis/plotall." This script uses the "R" statistical language environment to make plots using the scripts created in the post analysis phase. The script also uses plotting utilities (based on gnuplot and perl) from an earlier revision of this Recommendation to create plots of stream flow latency and packet loss. The "R" based plotting utilities are used for the TCP streams, while the gnuplot utilities are used for the UDP streams. + +## A.13 PCAP file list + +The simulator input PCAP files are in the dce/source/ns-3-dce/pcap/ subdirectory. Since these files are large, they are typically distributed separately from the model source code, and often the pcap subdirectory is a soft-link to a separate directory. Here is a list of typical input PCAP files. + +``` +pcap/HD_cbr.pcap +pcap/HD_vbr.pcap +pcap/SD_cbr.pcap +pcap/SD_vbr.pcap +``` + +pcap/voip\_g729\_fwd.pcap +pcap/voip\_g729\_rev.pcap +pcap/ipfax\_v34\_t38\_fwd.pcap +pcap/ipfax\_v34\_t38\_rev.pcap + +## A.14 Test case file list + +The individual test case parameter files are in the sim/tc directory: + +./tc/Dp1-t.param +./tc/Dp2-t.param +./tc/Dp3-t.param +./tc/Dp4-t.param +./tc/Dp5-t.param +./tc/Dp6-t.param +./tc/Dp7-t.param +./tc/Du1-t.param +./tc/Du2-t.param +./tc/Du3-t.param +./tc/Du4-t.param +./tc/Du5-t.param +./tc/Du6-t.param +./tc/Du7-t.param +./tc/Dw1-t.param +./tc/Dw2-t.param +./tc/Dw3-t.param +./tc/Dw4-t.param +./tc/Dw5-t.param +./tc/Dw6-t.param +./tc/Dw7-t.param +./tc/Dw8-t.param +./tc/Gp1-t.param +./tc/Gp2-t.param +./tc/Gp3-t.param +./tc/Gp4-t.param +./tc/Gp5-t.param +./tc/Gp6-t.param +./tc/Gp7-t.param +./tc/Gu1-t.param +./tc/Gu2-t.param +./tc/Gu3-t.param +./tc/Gu4-t.param +./tc/Gu5-t.param +./tc/Gu6-t.param +./tc/Gu7-t.param +./tc/Gw1-t.param +./tc/Gw2-t.param +./tc/Gw3-t.param +./tc/Gw4-t.param +./tc/Gw5-t.param +./tc/Gw6-t.param +./tc/Gw7-t.param +./tc/Gw8-t.param + +The output results for each test case are placed in a subdirectory of the "./out" directory. For each PacketMonitorPCAP that is configured in the parameter file, there is an output PCAP file and an output ".out" file (described below). + +./tc/common.tcl + +There are four convenience scripts to help run the simulation and plot results: + +``` +run_core2lan.ss +runall +postall +plotall +``` + +## A.15 Common TCL file + +There is one TCL support file that helps with setting up simulation parameters: + +``` +./tc/common.tcl +``` + +The common TCL support file "common.tcl" helps simplify the process of setting variables for the PCAP generators and monitors. + +The first thing that the common.tcl file does is create the output directory and set the variable \$outdir: + +``` +# - - - - - +# Create the output directory +# - - - - - +set outroot "out" +set outdir [file join $outroot [file rootname [file tail $paramfile]]] +file mkdir $outdir +``` + +The next routine "gset" is a general purpose routine for setting a global variable: + +``` +# - - - - - +# gset -- set a variable at global scope +# - - - - - +proc gset {name value} { + upvar \#0 $name $name + set $name $value +} +``` + +The next routine defines parameters for a PCAP generator: + +``` +# - - - - - +# Define parameters for a PCAP Generator +# - - - - - +proc PCAP_Generator {name file {start ""} {bwscale ""} {ppm ""} \ + {rand ""} {prio ""} {rept ""} {PIR ""} {PBS ""}} { + gset ${name}_FileName "pcap/$file.pcap" + if {$start != ""} { gset ${name}_StartDelay $start } + if {$bwscale != ""} { gset ${name}_BW_Scale $bwscale } + if {$ppm != ""} { gset ${name}_PPM_Offset $ppm } + if {$rand != ""} { gset ${name}_Randomness $rand } + if {$prio != ""} { gset ${name}_Priority $prio } + if {$rept != ""} { gset ${name}_RepeatCnt $rept } + if {$PIR != ""} { gset ${name}_ShaperPIR $PIR } + if {$PBS != ""} { gset ${name}_ShaperPBS $PBS } +} +``` + +The next routine defines parameters for a PCAP monitor: + +``` +# - - - - - +# Define parameters for a PCAP Monitor +# - - - - - +proc PCAP_Monitor {name file} { + global outdir + gset ${name}_OutFileName "$outdir/$file.out" + gset ${name}_PCAPFileName "$outdir/$file.pcap" +} +``` + +The next routines help to set network parameters for the access link: + +``` + +# - - - - - +# Set Global Vars for Access Link Parameters +# - - - - - +proc _Access_Params {name + {SpeedDown ""} + {SpeedUp ""} + {BER_Fwd ""} + {BER_Rev ""} + {LatencyDown ""} + {LatencyUp ""}} { + if {$SpeedDown != ""} { gset ${name}_SpeedDown $SpeedDown } + if {$SpeedUp != ""} { gset ${name}_SpeedUp $SpeedUp } + if {$BER_Fwd != ""} { gset ${name}_BER_Fwd $BER_Fwd } + if {$BER_Rev != ""} { gset ${name}_BER_Rev $BER_Rev } + if {$LatencyDown != ""} { gset ${name}_LatencyDown $LatencyDown } + if {$LatencyUp != ""} { gset ${name}_LatencyUp $LatencyUp } + if {$ReorderProb != ""} { gset RO_Fwd_Prob $ReorderProb } + if {$ReorderProb != ""} { gset RO_Rev_Prob $ReorderProb } +} +# - - - - - +# Select a set of access link parameters based on name +# - - - - - +proc Set_Access_Params {paramset} { + # Node SpdDn SpdUp BER_Fwd BER_Rev LatcyDn LatcyUp + if {$paramset == "dsl_w1"} { _Access_Params RACC 33e6 3e6 1e-8 1e-8 1e-3 1e-3 } + } elseif {$paramset == "dsl_w2"} { _Access_Params RACC 33e6 3e6 1e-8 1e-8 1e-3 1e-3 } + } elseif {$paramset == "dsl_w3"} { _Access_Params RACC 33e6 3e6 1e-8 1e-8 1e-3 1e-3 } + } elseif {$paramset == "dsl_w4"} { _Access_Params RACC 22e6 2e6 1e-8 1e-8 1e-3 1e-3 } + } elseif {$paramset == "dsl_w5"} { _Access_Params RACC 16e6 1e6 1e-7 1e-7 1e-3 1e-3 } + } elseif {$paramset == "dsl_w6"} { _Access_Params RACC 16e6 1e6 1e-7 1e-7 1e-3 1e-3 } + } elseif {$paramset == "dsl_w7"} { _Access_Params RACC 16e6 1e6 1e-7 1e-7 1e-3 1e-3 } + } elseif {$paramset == "dsl_w8"} { _Access_Params RACC 10e6 1e6 1e-7 1e-7 1e-3 1e-3 } + } elseif {$paramset == "pon_w1"} { _Access_Params RACC 50e6 25e6 1e-12 1e-12 1e-3 1e-3 } + } elseif {$paramset == "pon_w2"} { _Access_Params RACC 50e6 25e6 1e-12 1e-12 1e-3 1e-3 } + } elseif {$paramset == "pon_w3"} { _Access_Params RACC 35e6 25e6 1e-11 1e-11 1e-3 1e-3 } + } elseif {$paramset == "pon_w4"} { _Access_Params RACC 35e6 25e6 1e-11 1e-11 1e-3 1e-3 } + } elseif {$paramset == "pon_w5"} { _Access_Params RACC 25e6 25e6 1e-10 1e-10 1e-3 1e-3 } + } elseif {$paramset == "pon_w6"} { _Access_Params RACC 25e6 25e6 1e-9 1e-9 1e-3 1e-3 } + } elseif {$paramset == "pon_w7"} { _Access_Params RACC 25e6 25e6 1e-9 1e-9 1e-3 1e-3 } + } elseif {$paramset == "pon_w8"} { _Access_Params RACC 15e6 5e6 1e-9 1e-9 1e-3 1e-3 } + } elseif {$paramset == "pon_p1_u1"} { _Access_Params RACC 35e6 35e6 1e-12 1e-12 1e-3 1e-3 } + } elseif {$paramset == "pon_p2_u2"} { _Access_Params RACC 35e6 15e6 1e-12 1e-12 1e-3 1e-3 } + } elseif {$paramset == "pon_p3_u3"} { _Access_Params RACC 25e6 25e6 1e-11 1e-11 1e-3 1e-3 } + } elseif {$paramset == "pon_p4_u4"} { _Access_Params RACC 15e6 5e6 1e-9 1e-9 1e-3 1e-3 } + } elseif {$paramset == "pon_p5_u5"} { _Access_Params RACC 5e6 2e6 1e-9 1e-9 1e-3 1e-3 } + } elseif {$paramset == "pon_p6_u6"} { _Access_Params RACC 15e6 5e6 1e-9 1e-9 1e-3 1e-3 } + } elseif {$paramset == "pon_p7_u7"} { _Access_Params RACC 5e6 2e6 1e-9 1e-9 1e-3 1e-3 } + } elseif {$paramset == "dsl_p1_u1"} { _Access_Params RACC 24e6 3.0e6 1e-8 1e-8 1e-3 1e-3 } + } elseif {$paramset == "dsl_p2_u2"} { _Access_Params RACC 18e6 1.5e6 1e-7 1e-7 1e-3 1e-3 } + } elseif {$paramset == "dsl_p3_u3"} { _Access_Params RACC 12e6 1.5e6 1e-7 1e-7 1e-3 1e-3 } + } elseif {$paramset == "dsl_p4_u4"} { _Access_Params RACC 6e6 1.0e6 1e-6 1e-6 1e-3 1e-3 } + } elseif {$paramset == "dsl_p5_u5"} { _Access_Params RACC 3e6 1.0e6 1e-6 1e-6 1e-3 1e-3 } + } elseif {$paramset == "dsl_p6_u6"} { _Access_Params RACC 6e6 1.0e6 1e-6 1e-6 1e-3 1e-3 } + } elseif {$paramset == "dsl_p7_u7"} { _Access_Params RACC 3e6 1.0e6 1e-6 1e-6 1e-3 1e-3 } + } elseif {$paramset == "core_only"} { _Access_Params RACC 1e9 1e9 1e-12 1e-12 0 0 } + } else { + error "ERROR: Invalid Net_Param name $paramset." + } +} + +``` + +The next routines help to set network parameters for the core: + +``` + +# - - - - - +# Set Global Vars for Access Link Parameters +# - - - - - +proc _Core_Params {numsw ""} + {Latency ""} + {Speed ""}} { + if {$numsw != ""} { gset NumCoreSW $numsw } + if {$Latency != ""} { gset CORE_Latency $Latency } + if {$Speed != ""} { gset CORE_Speed $Speed } +} + +``` + +``` + +} +# - - - - - +# Select a set of core parameters based on name +# - - - - - +proc Set_Core_Params {paramset} { + # NumCoreSW Latency Speed + if {$paramset == "w1"} { _Core_Params 3 10e-3 1e9 +} elseif {$paramset == "w2"} { _Core_Params 4 25e-3 1e9 +} elseif {$paramset == "w3"} { _Core_Params 5 50e-3 1e9 +} elseif {$paramset == "w4"} { _Core_Params 6 75e-3 1e9 +} elseif {$paramset == "w5"} { _Core_Params 7 85e-3 1e9 +} elseif {$paramset == "w6"} { _Core_Params 8 100e-3 1e9 +} elseif {$paramset == "w7"} { _Core_Params 9 125e-3 1e9 +} elseif {$paramset == "w8"} { _Core_Params 10 150e-3 1e9 +} elseif {$paramset == "p1_u1"} { _Core_Params 3 10e-3 1e9 +} elseif {$paramset == "p2_u2"} { _Core_Params 4 25e-3 1e9 +} elseif {$paramset == "p3_u3"} { _Core_Params 5 50e-3 1e9 +} elseif {$paramset == "p4_u4"} { _Core_Params 8 75e-3 1e9 +} elseif {$paramset == "p5_u5"} { _Core_Params 10 100e-3 1e9 +} elseif {$paramset == "p6_u6"} { _Core_Params 12 200e-3 1e9 +} elseif {$paramset == "p7_u7"} { _Core_Params 15 250e-3 1e9 +} elseif {$paramset == "core_only"} { _Core_Params 5 100e-3 1e9 +} else { + error "ERROR: Invalid Net_Param name $paramset." +} +} + +# - - - - - +# Other Misc parameter settings +# - - - - - +set CORESW_BufSizeBytes [expr 65*1518] +set DSLAM_BufSizeBytes [expr 65*1518] +set Firewall_BufSizeBytes [expr 65*1518] +set Modem_BufSizeBytes [expr 65*1518] +set RLAN_Speed 100E6 +# - - - - - +# Set Default Simulation length +# - - - - - +set SimLengthSeconds [expr 10*60] + +``` + +# **Annex B** + +## **C++ source code of the discrete event simulator** + +(This annex forms an integral part of this Recommendation.) + +The C++ source code of the simulator is included in simulator.tar.gz of the electronic attachment (Annex H). + +# Annex C + +## Packet capture files of interfering traffic + +(This annex forms an integral part of this Recommendation.) + +Table C.1 lists the pcap files used in the standard test cases. These files are included in folder ./pcap in the electronic attachment (Annex H). + +**Table C.1 – PCAP files of interfering traffic** + +| QoS | PCAP file | Data size | Packets | Duration | Avg Pkt size | Packet rate | Avg bit rate | 5s peak | 1s peak | Description | +|-----|---------------|-----------|---------|----------|--------------|-------------|--------------|----------|----------|--------------------------------------------------| +| 2 | HD_cbr | 275756340 | 201282 | 142 | 1370 | 1419 | 15555964 | 15558816 | 15574160 | High definition IPTV flow, constant bit rate | +| 2 | HD_vbr | 196918938 | 143737 | 142 | 1370 | 1014 | 11112049 | 13112544 | 18555280 | High definition IPTV flow, variable bit rate | +| 2 | SD_cbr | 274844350 | 200617 | 285 | 1370 | 703 | 7702130 | 7704880 | 7715840 | Standard definition IPTV flow, constant bit rate | +| 2 | SD_vbr | 197616080 | 144246 | 285 | 1370 | 507 | 5553410 | 6608880 | 8789920 | Standard definition IPTV flow, variable bit rate | +| 1 | voip_g729_fwd | 603120 | 7180 | 215 | 84 | 33 | 22406 | 22444 | 22848 | [ITU-T G.729] voice-over-IP | +| 1 | voip_g729_rev | 602784 | 7176 | 215 | 84 | 33 | 22403 | 22444 | 22848 | | + +Figures C.1 to C.3 show the bit rate of each pcap stream averaged over 1-second and 5-second non-overlapping windows. + + + +Figure C.1: IPTV HD Bitstreams. A line graph showing bit rate in bits/sec over 150 seconds. The y-axis ranges from 0 to 20,000,000 bits/sec. The x-axis ranges from 0 to 150 seconds. Four data series are plotted: HD\_cbr (1s) (blue line with circles), HD\_cbr (5s) (yellow dashed line with triangles), HD\_vbr (1s) (red line with crosses), and HD\_vbr (5s) (green dashed line with plus signs). The HD\_cbr series are relatively flat around 16,000,000 bits/sec. The HD\_vbr series show significant fluctuations, with peaks around 18,000,000 bits/sec and troughs around 2,000,000 bits/sec. + +Figure C.1 – IPTV HD input PCAP bandwidth + + + +Figure C.2: IPTV SD Bitstreams. A line graph showing bit rate in bits/sec over 300 seconds. The y-axis ranges from 0 to 10,000,000 bits/sec. The x-axis ranges from 0 to 300 seconds. Four data series are plotted: SD\_cbr (1s) (blue line with circles), SD\_cbr (5s) (yellow dashed line with triangles), SD\_vbr (1s) (red line with crosses), and SD\_vbr (5s) (green dashed line with plus signs). The SD\_cbr series are relatively flat around 8,000,000 bits/sec. The SD\_vbr series show significant fluctuations, with peaks around 9,000,000 bits/sec and troughs around 1,000,000 bits/sec. + +Figure C.2 – IPTV SD input PCAP bandwidth + + + +Figure C.3: G.729 VoIP. A line graph showing bit rate in bits/sec over 200 seconds. The y-axis ranges from 0 to 25,000 bits/sec. The x-axis ranges from 0 to 200 seconds. Four data series are plotted: voip\_g729\_fwd (1s) (blue line with circles), voip\_g729\_fwd (5s) (yellow dashed line with triangles), voip\_g729\_rev (1s) (red line with crosses), and voip\_g729\_rev (5s) (green dashed line with plus signs). All series are relatively flat around 22,000 bits/sec. + +Figure C.3 – Voice over IP input PCAP bandwidth + +# Annex D + +## Example output plots for a typical test case + +(This annex forms an integral part of this Recommendation.) + +The baseline test cases of the previous edition of this Recommendation have been modified and run using the ns-3 simulator of Annex B. The goal of this simulator has been to more accurately characterize the residual best effort "goodput". To accomplish this, the simulator utilizes iPerf, a synthetic TCP load generation program, to replace the unmanaged best traffic of the original test cases. + +The test cases are executed in three scenarios: + +- a) Down: The iPerf flow is run in the downstream direction and directly competes with managed traffic. +- b) Up: The iPerf flow is run unencumbered in the upstream direction. While the data stream has no competition, the acknowledgement packets do compete since they must traverse the downstream path. +- c) Bidi: iPerf flows are present in both the upstream and downstream directions. + +This annex presents the plots that are available for each test case in the electronic attachment. For the purposes of this example, the plots are presented for the bidirectional scenario of the Dw4-t test case. + +The generated plots fall into three categories: + +- Overall flow summaries: Violin plots (Figures D.1.1 to D.1.8) allow for comparison of the distribution of one-way delay for the individual flows. Further plots are also provided for specific comparisons between the VoIP, DTV, and TCP (iPerf) flows. Bandwidth plots are also provided for the different flows in the test case with 1sec and 10sec bandwidth averaging to help visualize the burstiness of the traffic. These charts are also presented as line charts and stacked area charts to help visualize each stream's bandwidth contributions to the overall traffic mix. +- Legacy plots for unidirectional managed flows: This series of plots (Figures D.2.1 to D.2.10) were the same ones presented in the previous revision of this Recommendation. These plots capture the packet delay, drop, and distributions for the managed flows of the test case. +- Unmanaged TCP flow (iPerf) summaries: The TCP flows are characterized by a series of plots (Figures D.3.1 to D.3.7) showing the bandwidth, delay, and round-trip-time (RTT) of the flow. + +## D.1 Overall Flow Summaries + + + +Figure D.1.1 is a box plot showing delay distributions for various flow types. The y-axis is labeled 'Delay (ms)' and has major ticks at 100 and 1000. The x-axis categories are HDTV1D, SDTV1D, SDTV2D, VoIP1D, VoIP1U, iPerfD, and iPerfU. The plot title is 'bidi: Dw4-t (Min=76.05, Max=2792.53)'. Most flow types show low delay distributions, while iPerfU shows a significantly higher median delay and more variability. + +Delay distributions for all flows + +Figure D.1.1 – Delay distributions for all flows + + + +Figure D.1.2 is a box plot showing delay distributions for iPerf flows. The y-axis is labeled 'Delay (ms)' and has major ticks at 100 and 1000. The x-axis categories are iPerfD and iPerfU. The plot title is 'bidi: Dw4-t (Min=76.77, Max=2792.53)'. iPerfU shows a higher median delay and more variability compared to iPerfD. + +Delay distributions for iPerf flows + +Figure D.1.2 – Delay distributions for iPerf flows + + + +Figure D.1.3 is a box plot showing delay distributions for VoIP flows. The y-axis is labeled 'Delay (ms)' and has major ticks at 100 and 1000. The x-axis categories are VoIP1D and VoIP1U. The plot title is 'bidi: Dw4-t (Min=76.05, Max=88.36)'. Both VoIP1D and VoIP1U show low delay distributions, with VoIP1U having a slightly higher median delay. + +Delay distributions for VoIP flows + +Figure D.1.3 – Delay distributions for VoIP flows + + + +Figure D.1.4 is a box plot showing delay distributions for DTV flows. The y-axis is labeled 'Delay (ms)' and has major ticks at 100 and 1000. The x-axis categories are HDTV1D, SDTV1D, and SDTV2D. The plot title is 'bidi: Dw4-t (Min=76.8, Max=103.41)'. All three flow types show very low delay distributions, with HDTV1D having the highest median delay among them. + +Delay distributions for DTV flows (if present) + +Figure D.1.4 – Delay distributions for DTV flows (if present) + + + +Line chart titled 'bidi: Dw4-t Per-Flow BW (1s avg)' showing bandwidth usage over time for various flows. The top graph (199) shows high-frequency spikes for flow x41967 (pink), while other flows remain relatively flat. The bottom graph (315) shows more stable usage across multiple flows including x41967, x49153, x49154, x49155, x49156, x50002, and x60057. + +Figure D.1.5 – Bandwidth per flow/port (1s avg) + + + +Stacked area chart titled 'bidi: Dw4-t Per-Flow BW (1s avg)' showing the cumulative bandwidth usage over time. The top graph (199) shows a dense stack of spikes, primarily from flow x41967. The bottom graph (315) shows a more consistent stacked area representing the combined usage of all flows. + +Figure D.1.6 – Bandwidth per flow/port stacked (1s avg) + + + +Line chart titled 'bidi: Dw4-t Per-Flow BW (10s avg)' showing smoothed bandwidth usage over time. The top graph (199) shows smoother lines for flows x41967 and x49153. The bottom graph (315) shows stable, low-level usage for most flows, with a notable spike for flow x49154 (green) at the end of the period. + +Figure D.1.7 – Bandwidth per flow/port (10s avg) + + + +Stacked area chart titled 'bidi: Dw4-t Per-Flow BW (10s avg)' showing smoothed cumulative bandwidth usage. The top graph (199) shows a smoother stacked area compared to the 1s average. The bottom graph (315) shows a very stable stacked area for the combined flows. + +Figure D.1.8 – Bandwidth per flow/port stacked (10s avg) + +## D.2 Legacy plots for unidirectional managed flows (where present) + + + +This histogram shows the distribution of packet delays for the Dw4-t-HDTV1\_Down flow. The x-axis represents 'Delay(millisecond)' from 75 to 105. The y-axis represents 'Count' on a logarithmic scale from 1 to 100,000. The data is highly concentrated between 75 and 80 milliseconds, with a peak count of approximately 10,000. There are several smaller spikes at higher delay values, notably around 80, 85, 90, 95, and 100 milliseconds. + +Dw4-t-HDTV1\_Down (Packet Delay Variation Histogram) + +Figure D.2.1 – Downstream DTV flow packet delay variation + + + +This dual-axis plot shows delay and drop statistics over time for the Dw4-t-HDTV1\_Down flow. The top y-axis is 'Delay(millisecond)' (75-105) and the bottom y-axis is 'Drop/sec' (1-10). The x-axis is 'Time(H:M:S)' from 00:00:00 to 00:10:00. The delay data is shown as a dense blue line around 77 milliseconds. The drop data is shown as red vertical bars. A text label indicates 'Drop Total = 41'. + +Dw4-t-HDTV1\_Down (Delay and Drop) + +Figure D.2.2 – Downstream DTV flow packet delay-loss plot + + + +This histogram shows the distribution of packet delays for the Dw4-t-SDTV1\_Down flow. The x-axis represents 'Delay(millisecond)' from 75 to 105. The y-axis represents 'Count' on a logarithmic scale from 1 to 10,000. The data is highly concentrated between 75 and 80 milliseconds, with a peak count of approximately 10,000. There are a few isolated spikes at higher delay values, notably around 80, 100, and 102 milliseconds. + +Dw4-t-SDTV1\_Down (Packet Delay Variation Histogram) + +Figure D.2.3 – Downstream DTV flow packet delay variation + + + +This dual-axis plot shows delay and drop statistics over time for the Dw4-t-SDTV1\_Down flow. The top y-axis is 'Delay(millisecond)' (75-105) and the bottom y-axis is 'Drop/sec' (1-10). The x-axis is 'Time(H:M:S)' from 00:00:00 to 00:10:00. The delay data is shown as a dense blue line around 77 milliseconds. The drop data is shown as red vertical bars. A text label indicates 'Drop Total = 16'. + +Dw4-t-SDTV1\_Down (Delay and Drop) + +Figure D.2.4 – Downstream DTV flow packet delay-loss plot + + + +Dw4-t-SDTV2\_Down (Packet Delay Variation Histogram) + +Dw4-t-SDTV2\_Down (Packet Delay Variation Histogram) showing a distribution of packet delays in milliseconds. The x-axis ranges from 75 to 105 ms, and the y-axis (Count) is logarithmic from 1 to 100,000. The distribution is highly skewed towards lower delays, with a peak around 77-78 ms. + +Figure D.2.5 – Downstream DTV flow packet delay variation + + + +Dw4-t-SDTV2\_Down (Delay and Drop) + +Dw4-t-SDTV2\_Down (Delay and Drop) showing delay in milliseconds and drop rate over time. The top plot shows delay fluctuating around 77 ms. The bottom plot shows drop rate, with a total of 8 drops recorded over the 10-minute period. + +Figure D.2.6 – Downstream DTV flow packet delay-loss plot + + + +Dw4-t-VoIP1\_Rev (Delay) + +Dw4-t-VoIP1\_Rev (Delay) showing delay in milliseconds over time. The y-axis ranges from 76 to 83 ms. The plot shows a dense cloud of points, indicating significant delay variation. A note at the bottom right indicates 'No Dropped Packets'. + +Figure D.2.7 – Downstream VoIP flow packet delay variation + + + +Dw4-t-VoIP1\_Rev (Packet Delay Variation Histogram) + +Dw4-t-VoIP1\_Rev (Packet Delay Variation Histogram) showing the distribution of packet delays in milliseconds. The x-axis ranges from 76 to 83 ms, and the y-axis (Count) is logarithmic from 1 to 1,000. The distribution is relatively uniform across the range, with a slight peak around 77 ms. + +Figure D.2.8 – Downstream VoIP flow packet delay-loss plot + + + +This histogram displays the distribution of packet delays for the Dw4-t-VoIP1\_Rev flow. The x-axis represents 'Delay(millisecond)' ranging from 76 to 83. The y-axis represents 'Count' on a logarithmic scale from 1 to 1000. The data shows a high frequency of packets with delays between 76.5 and 82.5 milliseconds, with a peak count near 1000 at approximately 76.8 milliseconds. The distribution is relatively uniform across the delay range, with a slight decrease in count towards the ends. + +Dw4-t-VoIP1\_Rev (Packet Delay Variation Histogram) showing Count vs Delay(millisecond). + +**Figure D.2.9 – Upstream VoiP flow packet delay variation** + + + +This scatter plot shows the delay variation over time for the Dw4-t-VoIP1\_Rev flow. The x-axis represents 'Time(H:M:S)' from 00:00:00 to 00:10:00. The y-axis represents 'Delay(millisecond)' from 76 to 83. The plot contains numerous data points scattered between 76.5 and 82.5 milliseconds across the entire time period. A note at the bottom right indicates '(No Dropped Packets)'. The delay appears consistent throughout the observed duration. + +Dw4-t-VoIP1\_Rev (Delay) showing Delay(millisecond) vs Time(H:M:S). + +**Figure D.2.10 – Upstream VoiP flow packet delay-loss plot** + +## D.3 Unmanaged TCP flow (iPerf) summaries + + + +Bidirectional iPerf: 1-way BW: bidi: Dw4-t +(Min=0, Max=8.38, Mean=2.2, Median=1.94, StdDev=1.37) + +Figure D.3.1: Bidirectional iPerf 1-way Bandwidth plot. The y-axis is Bandwidth (Mbit) on a log scale from 0.1 to 10.0. The x-axis is time (sec) from 0 to 600. The plot shows a dense cloud of data points between 0.1 and 10 Mbit/s. Summary statistics: Min=0, Max=8.38, Mean=2.2, Median=1.94, StdDev=1.37. + +**Figure D.3.1 – TCP bandwidth/delay/RTT** + + + +bidi: Dw4-t + +Figure D.3.2: Bidirectional iPerf 1-way Bandwidth, Delay, and RTT plots. The top plot shows Bandwidth (Mbit/s) for 'up' and 'dwn' streams. The middle plot shows Delay (ms) for 'up' and 'dwn' streams. The bottom plot shows RTT (ms) for 'up' and 'dwn' streams. All plots have an x-axis from 0 to 600 seconds. + +**Figure D.3.2 – TCP bandwidth/delay/RTT (upstream/downstream for bidirectional case)** + + + +bidi: Dw4-t + +Figure D.3.3: iPerf Bandwidth, Delay, and RTT stacked plots. The top plot shows Bandwidth (Mbit/s), the middle shows Delay (ms), and the bottom shows RTT (ms). The x-axis is time (sec) from 0 to 600. + +**Figure D.3.3 – iPerf bandwidth** + + + +iPerf: 1-way Delay: bidi: Dw4-t +(Min=76.03, Max=2795.86, Mean=250.91, Median=244.91, StdDev=172.19) + +Figure D.3.4: iPerf Delay plot. The y-axis is Avg Delay (ms) on a log scale from 100 to 1000. The x-axis is time (sec) from 0 to 600. Summary statistics: Min=76.03, Max=2795.86, Mean=250.91, Median=244.91, StdDev=172.19. + +**Figure D.3.4 – iPerf delay** + + + +iPerf: 1-way Delay:bidi: Dw4-t +(Min=76.03, Max=2795.86, Mean=250.91, Median=244.91, StdDev=172.19) + +Violin plot of iPerf 1-way delay distribution for 'up' and 'down' directions. The y-axis is 'Avg Delay (ms)' on a log scale from 100 to 1000. The plot shows two violins: a red one for 'up' and a blue one for 'down'. Summary statistics are provided at the top: Min=76.03, Max=2795.86, Mean=250.91, Median=244.91, StdDev=172.19. + +Figure D.3.5 – iPerf delay distribution (violin plot) + + + +iPerf: 1-way Delay:bidi: Dw4-t +(Min=76.03, Max=2795.86, Mean=250.91, Median=244.91, StdDev=172.19) + +Cumulative Distribution Function (CDF) plot of iPerf 1-way delay. The x-axis is 'Avg Delay (ms)' on a log scale from 100 to 1000. The y-axis is the cumulative probability from 0.00 to 1.00. Two curves are shown: a blue curve for 'up' and a red curve for 'down'. Summary statistics are provided at the top: Min=76.03, Max=2795.86, Mean=250.91, Median=244.91, StdDev=172.19. + +Figure D.3.6 – iPerf delay CDF + + + +iPerf: RTT: bidi: Dw4-t +(Min=152.3, Max=3320.01, Mean=480.71, Median=482.09, StdDev=104.76) + +Line graph of iPerf RTT over time. The x-axis is 'time (sec)' from 0 to 600. The y-axis is 'RTT (ms)' on a log scale from 100 to 1000. Two lines are plotted: a red line for 'up' and a blue line for 'down'. Summary statistics are provided at the top: Min=152.3, Max=3320.01, Mean=480.71, Median=482.09, StdDev=104.76. + +Figure D.3.7 – iPerf delay RTT + +# Annex E + +## Summary of simulation output plots + +(This annex forms an integral part of this Recommendation.) + +This annex describes a series of summary plots provided for the six technology-scenario combinations generated in this Recommendation. The purpose of these plots is to provide a quick reference to aid in the selection of specific test cases of interest. The plots are provided in their entirety in this annex as well as in the electronic attachment. The naming convention of plot files is as follows: + +- \$TECH – Technology (D=DSL, G=GPON); +- \$SC – iPerf Scenario: (out.bidi, out.dwn, out.up). + +**Table E.1 – Summary output plot file naming convention** + +| File Name | Description | +|------------------------|------------------------------------------------------------------| +| /\$TECH/\$SC | Technology-scenario directory | +| summary.png | Test case median delay-bandwidth points | +| cdfplt-01.png | One-way iPerf delay CDF by direction and management type | +| merge-01.png | One-way iPerf bandwidth by direction and management type | +| merge-02.png | One-way iPerf bandwidth (unmanaged cases) | +| merge-03.png | One-way iPerf bandwidth (partly managed cases) | +| merge-04.png | One-way iPerf bandwidth (well managed cases) | +| merge-05.png | One-way iPerf delay distribution (unmanaged cases) | +| merge-06.png | One-way iPerf delay distribution (well managed cases) | +| merge-07.png | One-way iPerf delay distribution (partly managed cases) | +| mngplt-01.png | Aggregate managed bandwidth (well and partly managed cases) | +| /\$TECH/\$SC/PDF | Directory containing .pdf versions of test case plots | +| /\$TECH/\$SC/PCAP | Directory containing .pcap files of test case traffic (optional) | +| /\$TECH/\$SC/cdf.csv | Data file for cdfplt-01.png | +| /\$TECH/\$SC/stats.csv | Data file for summary.png | +| /\$TECH/info.csv | Data file for Annex G Tables | + + + + + +Figure E.1.1.3: iPerf Unidirectional BW Scenario: out.bidi. A 2x3 grid of plots showing bandwidth over time (0 to 600 seconds) for Well Managed, Partly Managed, and Unmanaged cases. The top row shows individual stream bandwidths (0 to 3 Mbps) for streams Dw1 through Dw8. The bottom row shows the aggregate bandwidth (0 to 15 Mbps). + +Figure E.1.1.3 – One-way iPerf bandwidth by direction and management type + + + +Figure E.1.1.4: iPerf Unidirectional BW Scenario: out.bidi. A 2x1 grid of plots for the Unmanaged case. The top plot shows individual stream bandwidths (0 to 3 Mbps) for streams Du1 through Du7. The bottom plot shows the aggregate bandwidth (0 to 15 Mbps). + +Figure E.1.1.4 – One-way iPerf bandwidth (unmanaged cases) + + + +Figure E.1.1.5: iPerf Unidirectional BW Scenario: out.bidi. A 2x1 grid of plots for the Partly Managed case. The top plot shows individual stream bandwidths (0 to 3 Mbps) for streams Dp1 through Dp6. The bottom plot shows the aggregate bandwidth (0 to 12 Mbps). + +Figure E.1.1.5 – One-way iPerf bandwidth (partly managed cases) + + + +Figure E.1.1.6: iPerf Unidirectional BW Scenario: out.bidi. A 2x1 grid of plots for the Well Managed case. The top plot shows individual stream bandwidths (0 to 3 Mbps) for streams Dw1 through Dw8. The bottom plot shows the aggregate bandwidth (0 to 15 Mbps). + +Figure E.1.1.6 – One-way iPerf bandwidth (well managed cases) + + + +Figure E.1.1.7: One-way iPerf delay distribution (unmanaged cases). A violin plot showing delay distributions for seven hops (Du1 to Du7) for 'up' (red) and 'down' (blue) traffic. The y-axis is logarithmic, ranging from 10 to 1000 ms. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.bidi (Min=11.03, Max=1910.02)'. + +Figure E.1.1.7 – One-way iPerf delay distribution (unmanaged cases) + + + +Figure E.1.1.8: One-way iPerf delay distribution (well managed cases). A violin plot showing delay distributions for six hops (Dp1 to Dp6) for 'up' (red) and 'down' (blue) traffic. The y-axis is logarithmic, ranging from 10 to 1000 ms. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.bidi (Min=11.03, Max=4679.79)'. + +Figure E.1.1.8 – One-way iPerf delay distribution (well managed cases) + + + +Figure E.1.1.9: One-way iPerf delay distribution (partly managed cases). A violin plot showing delay distributions for eight hops (Dw1 to Dw8) for 'up' (red) and 'down' (blue) traffic. The y-axis is logarithmic, ranging from 10 to 1000 ms. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.bidi (Min=49.82, Max=5150.43)'. + +Figure E.1.1.9 – One-way iPerf delay distribution (partly managed cases) + + + +Figure E.1.1.10: Aggregate managed bandwidth (well and partly managed cases). A line graph showing bandwidth usage over 600 seconds for 'Partly Managed' and 'Well Managed' cases. The y-axis is 'Bandwidth (Mbit)' ranging from 0 to 20. The x-axis is 'time (sec)' ranging from 0 to 600. The legend lists various data flows: Dp1-t, Dp2-t, Dp3-t, Dp4-t, Dp5-t, Dw1-t, Dw2-t, Dw3-t, Dw4-t, Dw5-t, Dw6-t, Dw7-t, Dw8-t. + +Figure E.1.1.10 – Aggregate managed bandwidth (well and partly managed cases) + +### E.1.2 DSL upstream iPerf scenario + + + +The scatter plot shows the relationship between median bandwidth and median 1-way delay for different test cases. The x-axis represents 'Median 1-way Delay (ms)' from 200 to 800, and the y-axis represents 'Median Bandwidth (Kbit/s)'. Data points are labeled with test case names and categorized by management type. + +| Test Case | Management Type | Median 1-way Delay (ms) | Median Bandwidth (Kbit/s) | +|-----------|-----------------|-------------------------|---------------------------| +| Du4 | Unmanaged | ~200 | ~100 | +| Du5 | Unmanaged | ~220 | ~80 | +| Dp5 | Partly Managed | ~230 | ~60 | +| Du6 | Unmanaged | ~250 | ~40 | +| Dp6 | Partly Managed | ~260 | ~30 | +| Du7 | Unmanaged | ~280 | ~20 | +| Dp12w3 | Well Managed | ~300 | ~400 | +| Dw4 | Well Managed | ~400 | ~300 | +| Dp3 | Partly Managed | ~420 | ~250 | +| Dw5 | Well Managed | ~700 | ~150 | +| Dw8 | Well Managed | ~750 | ~150 | + +Scatter plot titled 'iPerf Bandwidth-Delay Scenario: out.up' showing Median Bandwidth (Kbit/s) vs. Median 1-way Delay (ms) for various test cases. The plot is categorized into Partly Managed (red), Unmanaged (green), and Well Managed (blue). + +Figure E.1.2.1 – Test case median delay-bandwidth points + + + +The CDF plot shows the cumulative distribution function of 1-way delay for different test cases. The x-axis represents '1-way delay (ms)' on a logarithmic scale from 100 to 1000, and the y-axis represents the cumulative probability from 0.00 to 1.00. The plot is divided into three sections: Partly Managed (red), Unmanaged (green), and Well Managed (blue). + +| Management Type | Test Cases | +|-----------------|--------------------------------------------------------| +| Partly Managed | Dp2up, Dp3up, Dp4up, Dp5up, Dp6up | +| Unmanaged | Du1up, Du2up, Du3up, Du4up, Du5up, Du6up, Du7up | +| Well Managed | Dw1up, Dw2up, Dw3up, Dw4up, Dw5up, Dw6up, Dw7up, Dw8up | + +CDF plot titled 'iPerf Unidirectional delay CDF Scenario: out.up' showing the cumulative distribution function of 1-way delay (ms) for various test cases, categorized into Partly Managed, Unmanaged, and Well Managed groups. + +Figure E.1.2.2 – One-way iPerf delay CDF by direction and management type + + + +Figure E.1.2.3: iPerf Unidirectional BW Scenario: out.up. A multi-panel graph showing bandwidth (Mbps) over time (t) for three management types: Well Managed, Partly Managed, and Unmanaged. The Y-axis ranges from 0 to 3 Mbps. The X-axis ranges from 0 to 600 seconds. The legend indicates flows: Dw1, Dw2, Dw3, Dw4, Dw5, Dw6, Dw7, Dw8, Dp1, Dp2, Dp3, Dp4, Dp5, Dp6, Du1, Du2, Du3, Du4, Du5, Du6, Du7. In the 'Well Managed' panel, flows are stable at 1, 2, and 3 Mbps. In the 'Partly Managed' panel, flows show significant jitter and fluctuation. In the 'Unmanaged' panel, flows are highly congested and unstable. + +Figure E.1.2.3 – One-way iPerf bandwidth by direction and management type + + + +Figure E.1.2.4: iPerf Unidirectional BW Scenario: out.up. A single-panel graph for the 'Unmanaged' case. It shows highly volatile and congested bandwidth usage over time (t) from 0 to 600 seconds, with multiple colored lines representing different flows fluctuating rapidly between 0 and 3 Mbps. + +Figure E.1.2.4 – One-way iPerf bandwidth (unmanaged cases) + + + +Figure E.1.2.5: iPerf Unidirectional BW Scenario: out.up. A single-panel graph for the 'Partly Managed' case. It shows bandwidth usage over time (t) from 0 to 600 seconds. While some flows remain relatively stable, others exhibit significant jitter and fluctuation, indicating partial management effectiveness. + +Figure E.1.2.5 – One-way iPerf bandwidth (partly managed cases) + + + +Figure E.1.2.6: iPerf Unidirectional BW Scenario: out.up. A single-panel graph for the 'Well Managed' case. It shows very stable and consistent bandwidth usage over time (t) from 0 to 600 seconds, with flows maintaining their allocated rates (1, 2, and 3 Mbps) with minimal jitter. + +Figure E.1.2.6 – One-way iPerf bandwidth (well managed cases) + + + +iPerf Unidirectional Log Delay (ms) +Scenario: out.up +(Min=11.16, Max=1597.58) + +Du1 Du2 Du3 Du4 Du5 Du6 Du7 + +1000 + +100 + +10 + +5 + +up + +Figure E.1.2.7: Violin plot showing iPerf Unidirectional Log Delay (ms) for unmanaged cases (Du1 to Du7). The y-axis is logarithmic, ranging from 10 to 1000 ms. The plot shows that most delays are concentrated between 100 and 1000 ms, with some outliers reaching up to 1597.58 ms. + +**Figure E.1.2.7 – One-way iPerf delay distribution (unmanaged cases)** + + + +iPerf Unidirectional Log Delay (ms) +Scenario: out.up +(Min=11.16, Max=3339.83) + +Dp1 Dp2 Dp3 Dp4 Dp5 Dp6 + +1000 + +100 + +10 + +5 + +up + +Figure E.1.2.8: Violin plot showing iPerf Unidirectional Log Delay (ms) for well managed cases (Dp1 to Dp6). The y-axis is logarithmic, ranging from 10 to 1000 ms. The plot shows that most delays are concentrated between 10 and 100 ms, with some outliers reaching up to 3339.83 ms. + +**Figure E.1.2.8 – One-way iPerf delay distribution (well managed cases)** + + + +iPerf Unidirectional Log Delay (ms) +Scenario: out.up +(Min=11.16, Max=1494.13) + +Dw1 Dw2 Dw3 Dw4 Dw5 Dw6 Dw7 Dw8 + +1000 + +100 + +10 + +5 + +up + +Figure E.1.2.9: Violin plot showing iPerf Unidirectional Log Delay (ms) for unmanaged cases (Dw1 to Dw8). The y-axis is logarithmic, ranging from 10 to 1000 ms. The plot shows that most delays are concentrated between 100 and 1000 ms, with some outliers reaching up to 1494.13 ms. + +**Figure E.1.2.9 – One-way iPerf delay distribution (unmanaged cases)** + + + +Managed Bandwidth +Scenario: out.up + +Partly Managed Well Managed + +0.024 + +0.022 + +0.020 + +20 + +15 + +10 + +5 + +0 + +0 200 400 600 + +time (sec) + +Dp1-t Dp2-t Dp3-t Dp4-t Dp5-t Dp6-t Dw1-t Dw2-t Dw3-t Dw4-t Dw5-t Dw6-t Dw7-t Dw8-t + +Figure E.1.2.10: Time-series plot showing Managed Bandwidth (Mbps) over time (sec) for well managed cases. The plot is divided into two sections: 'Partly Managed' (0 to 600 sec) and 'Well Managed' (0 to 600 sec). The 'Partly Managed' section shows a relatively stable bandwidth around 0.024 Mbps. The 'Well Managed' section shows a more variable bandwidth, with peaks around 0.024 Mbps and troughs around 0.020 Mbps. + +**Figure E.1.2.10 – One-way iPerf delay distribution (well managed cases)** + +### E.1.3 DSL downstream iPerf scenario + + + +Figure E.1.3.1: iPerf Bandwidth-Delay plot for Scenario: out.dwn. The y-axis is Median Bandwidth (Mbit/s) on a log scale from 1 to 10. The x-axis is Median 1-way Delay (ms) from 100 to 200. Data points are labeled: Dw1, Dw2, Dw3, Dw4, Dw5, Dw6, Dw7, Dw8 (blue squares); Dp1, Dp2, Dp3, Dp4, Dp5, Dp6, Dp7 (red squares); and Du1, Du2, Du3, Du4, Du5, Du6, Du7 (green squares). A legend at the bottom indicates: Partly Managed (red), Unmanaged (green), and Well Managed (blue). + +Figure E.1.3.1 – Test case median delay-bandwidth points + + + +Figure E.1.3.2: iPerf Unidirectional delay CDF for Scenario: out.dwn. The y-axis is CDF from 0.00 to 1.00. The x-axis is 1-way delay (ms) on a log scale from 100 to 1000. The plot is divided into three sections: Partly Managed (yellow curves), Unmanaged (cyan curves), and Well Managed (magenta curves). A legend at the bottom lists 15 specific delay series: 3dwn, Dp4dwn, Dp5dwn, Dp6dwn, Du1dwn, Du2dwn, Du3dwn, Du4dwn, Du5dwn, Du6dwn, Du7dwn, Dw1dwn, Dw2dwn, Dw3dwn, Dw4dwn, Dw5dwn. + +Figure E.1.3.2 – One-way iPerf delay CDF by direction and management type + + + +Figure E.1.3.3: iPerf Unidirectional BW Scenario: out.dwn. A line graph showing bandwidth in Mbits over time (0 to 600) for three management scenarios: Well Managed, Partly Managed, and Unmanaged. The Y-axis ranges from 0 to 30 Mbits. The 'Well Managed' section shows multiple streams (Dw1-Dw7) maintaining high bandwidth (around 20-25 Mbits). The 'Partly Managed' section shows streams (Dp1-Dp6) with lower, more fluctuating bandwidth (around 10-15 Mbits). The 'Unmanaged' section shows streams (Du1-Du7) with very low bandwidth (mostly below 5 Mbits). + +Figure E.1.3.3 – One-way iPerf bandwidth by direction and management type + + + +Figure E.1.3.4: iPerf Unidirectional BW Scenario: out.dwn. A line graph showing bandwidth in Mbits over time (0 to 600) for the 'Unmanaged' case. The Y-axis ranges from 0 to 25 Mbits. It displays multiple data series (Du1-Du7) showing significant fluctuations and generally low bandwidth usage, with most values below 10 Mbits. + +Figure E.1.3.4 – One-way iPerf bandwidth (nmanaged cases) + + + +Figure E.1.3.5: iPerf Unidirectional BW Scenario: out.dwn. A line graph showing bandwidth in Mbits over time (0 to 600) for the 'Partly Managed' case. The Y-axis ranges from 0 to 25 Mbits. It displays multiple data series (Dp1-Dp6) showing moderate bandwidth usage with frequent spikes, generally staying between 5 and 15 Mbits. + +Figure E.1.3.5 – One-way iPerf bandwidth (partly managed cases) + + + +Figure E.1.3.6: iPerf Unidirectional BW Scenario: out.dwn. A line graph showing bandwidth in Mbits over time (0 to 600) for the 'Well Managed' case. The Y-axis ranges from 0 to 30 Mbits. It displays multiple data series (Dw1-Dw7) showing high and stable bandwidth usage, with most streams consistently between 15 and 25 Mbits. + +Figure E.1.3.6 – One-way iPerf bandwidth (well managed cases) + + + +Figure E.1.3.7: One-way iPerf delay distribution (unmanaged cases). A violin plot showing delay distributions for seven hops (Du1 to Du7). The y-axis is logarithmic, ranging from 10 to 1000 ms. The x-axis labels are Du1, Du2, Du3, Du4, Du5, Du6, Du7. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.dwn (Min=11.03, Max=1506.61)'. + +Figure E.1.3.7 – One-way iPerf delay distribution (unmanaged cases) + + + +Figure E.1.3.8: One-way iPerf delay distribution (well managed cases). A violin plot showing delay distributions for six hops (Dp1 to Dp6). The y-axis is logarithmic, ranging from 10 to 1000 ms. The x-axis labels are Dp1, Dp2, Dp3, Dp4, Dp5, Dp6. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.dwn (Min=11.03, Max=4681.56)'. + +Figure E.1.3.8 – One-way iPerf delay distribution (well managed cases) + + + +Figure E.1.3.9: One-way iPerf delay distribution (partly managed cases). A violin plot showing delay distributions for eight hops (Dw1 to Dw8). The y-axis is logarithmic, ranging from 10 to 1000 ms. The x-axis labels are Dw1, Dw2, Dw3, Dw4, Dw5, Dw6, Dw7, Dw8. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.dwn (Min=11.02, Max=806.92)'. + +Figure E.1.3.9 – One-way iPerf delay distribution (partly managed cases) + + + +Figure E.1.3.10: One-way iPerf delay distribution (well managed cases). A multi-panel figure. The top-left panel shows 'Partly Managed' bandwidth (Mbps) over time (0-600 sec) with a green line. The top-right panel shows 'Well Managed' bandwidth (Mbps) over time (0-600 sec) with a pink line. The bottom-left panel shows delay (ms) over time (0-600 sec) with a green line. The bottom-right panel shows delay (ms) over time (0-600 sec) with multiple colored lines. The legend at the bottom lists various delay series: Dp1-t, Dp2-t, Dp3-t, Dp4-t, Dp5-t, Dp6-t, Dw1-t, Dw2-t, Dw3-t, Dw4-t, Dw5-t, Dw6-t, Dw7-t, Dw8-t. + +Figure E.1.3.10 – One-way iPerf delay distribution (well managed cases) + +## E.2 GPON technology + +### E.2.1 GPON bidirectional iPerf scenario + + + +Scatter plot titled 'iPerf Bandwidth-Delay Scenario: out.bidi' showing Median Bandwidth (Mbit) on the y-axis (logarithmic scale from 1 to 10) versus Median 1-way Delay (ms) on the x-axis (linear scale from 0 to 500). Data points are labeled with identifiers like Ggw1, Ggw2, Ggw3, Ggw4, Ggw5, Ggw6, Ggw7, Ggw8, Gu1, Gu2, Gu3, Gu4, Gu5, Gu6, Gu7, Gp1, Gp2, Gp3, Gp4, Gp5, Gp6, Gp7. The legend indicates: Red square = Partly Managed, Green circle = Unmanaged, Blue triangle = Well Managed, Black cross = down&up. + +Figure E.2.1.1 – Test case median delay-bandwidth points + + + +A 2x3 grid of Cumulative Distribution Function (CDF) plots titled 'iPerf Unidirectional delay CDF Scenario: out.bidi'. The columns are labeled 'Partly Managed', 'Unmanaged', and 'Well Managed'. The top row shows the CDF for 'down' direction delays, and the bottom row shows the CDF for 'up' direction delays. The x-axis for all plots is '1-way delay (ms)' on a logarithmic scale from 100 to 1000. The y-axis for all plots is the cumulative probability from 0.00 to 1.00. Each plot contains multiple colored curves representing different test cases. A legend at the bottom lists the test cases: 1up - Ggw1down - Ggw2up - Ggw3down - Ggw4up - Ggw5down - Ggw6up - Ggw7down - Ggw8up - Gu1down - Gu2up - Gu3down - Gu4up - Gu5down - Gu6up - Gu7down - Gw1up - Gw2down - Gw3up - Gw4down - Gw5up - Gw6down - Gw7up - Gw8down - Gp1up - Gp2down - Gp3up - Gp4down - Gp5up - Gp6down - Gp7up. + +Figure E.2.1.2 – One-way iPerf delay CDF by direction and management type + + + +Figure E.2.1.3: A 2x3 grid of line graphs showing iPerf Unidirectional BW for 'Well Managed', 'Partly Managed', and 'Unmanaged' scenarios. The y-axis is 'Mbits' (0-30) and the x-axis is time 't' (0-600). The legend includes Gw1-Gw7 and Gp1-Gp7. The 'Well Managed' column shows stable bandwidth around 15-20 Mbits, while 'Unmanaged' shows more variability and spikes. + +Figure E.2.1.3 – One-way iPerf bandwidth by direction and management type + + + +Figure E.2.1.4: Two stacked line graphs for the 'Unmanaged' scenario. The top graph shows individual flows for Gw1-Gw7, with Gw1 (red) showing high variability. The bottom graph shows a summary of the same flows. Y-axis is 'Mbits' (0-30), x-axis is time 't' (0-600). + +Figure E.2.1.4 – One-way iPerf bandwidth (unmanaged cases) + + + +Figure E.2.1.5: Two stacked line graphs for the 'Partly Managed' scenario. The top graph shows individual flows for Gp1-Gp6. The bottom graph shows a summary. Y-axis is 'Mbits' (0-30), x-axis is time 't' (0-600). + +Figure E.2.1.5 – T one-way iPerf bandwidth (partly managed cases) + + + +Figure E.2.1.6: Two stacked line graphs for the 'Well Managed' scenario. The top graph shows individual flows for Gw1-Gw7. The bottom graph shows a summary. Y-axis is 'Mbits' (0-25), x-axis is time 't' (0-600). + +Figure E.2.1.6 – One-way iPerf bandwidth (well managed cases) + + + +Figure E.2.1.7: One-way iPerf delay distribution (unmanaged cases). A violin plot showing delay distributions for seven gateways (Gw1 to Gw7) for 'up' (red) and 'down' (blue) traffic. The y-axis is logarithmic, ranging from 10 to 1000 ms. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.bidi (Min=11.02, Max=3528.84)'. + +Figure E.2.1.7 – One-way iPerf delay distribution (unmanaged cases) + + + +Figure E.2.1.8: One-way iPerf delay distribution (well managed cases). A violin plot showing delay distributions for six gateways (Gp1 to Gp6) for 'up' (red) and 'down' (blue) traffic. The y-axis is logarithmic, ranging from 10 to 1000 ms. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.bidi (Min=11.02, Max=2331.4)'. + +Figure E.2.1.8 – One-way iPerf delay distribution (well managed cases) + + + +Figure E.2.1.9: One-way iPerf delay distribution (partly managed cases). A violin plot showing delay distributions for eight gateways (Gw1 to Gw8) for 'up' (red) and 'down' (blue) traffic. The y-axis is logarithmic, ranging from 10 to 1000 ms. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.bidi (Min=11.02, Max=2576.78)'. + +Figure E.2.1.9 – One-way iPerf delay distribution (partly managed cases) + + + +Figure E.2.1.10: One-way iPerf delay distribution (well managed cases). A multi-panel figure showing bandwidth usage over time (0 to 600 seconds) for 'Partly Managed' and 'Well Managed' scenarios. The top panels show bandwidth in Mbps (0.020 to 0.024), and the bottom panels show bandwidth in Mbps (0 to 20). The plot title is 'Managed Bandwidth Scenario: out.bidi'. + +Figure E.2.1.10 – One-way iPerf delay distribution (well managed cases) + +#### E.2.2 GPON upstream iPerf scenario + + + +The plot shows the relationship between median bandwidth and median 1-way delay for various test cases in a GPON upstream iPerf scenario. The y-axis represents 'Median Bandwidth (Mbit)' and the x-axis represents 'Median 1-way Delay (ms)'. The data points are labeled with test case identifiers: Gp1, Gw2, Gw3, Gp2, Gw4, Gw5, Gw6, Gw7, Gp4, Gw8, Gw6, Gw5, and Gu7. The legend indicates three management types: Partly Managed (red), Unmanaged (green), and Well Managed (blue). Most points show a downward trend, indicating that as the median 1-way delay increases, the median bandwidth tends to decrease. + +Figure E.2.2.1: iPerf Bandwidth-Delay plot for GPON upstream scenario. The y-axis is 'Median Bandwidth (Mbit)' and the x-axis is 'Median 1-way Delay (ms)'. Data points for various test cases (Gp1, Gw2, Gw3, Gp2, Gw4, Gw5, Gw6, Gw7, Gp4, Gw8, Gw6, Gw5, Gu7) are plotted. A legend at the bottom indicates management types: Partly Managed (red), Unmanaged (green), and Well Managed (blue). + +Figure E.2.2.1 – Test case median delay-bandwidth points + + + +The plot shows the cumulative distribution function (CDF) of one-way iPerf delay for various test cases in a GPON upstream scenario. The y-axis represents the CDF from 0.00 to 1.00, and the x-axis represents the 1-way delay in milliseconds on a logarithmic scale from 100 to 1000. The plot is divided into three sections based on management type: Partly Managed, Unmanaged, and Well Managed. Each section contains multiple curves representing different test cases: Gp2up, Gp3up, Gp4up, Gp5up, Gp6up, Gu1up, Gu2up, Gu3up, Gu4up, Gu5up, Gu6up, Gu7up, Gw1up, Gw2up, Gw3up, Gw4up, Gw5up, and Gw6up. The curves show that the delay distribution is generally lower for well-managed test cases compared to partly managed or unmanaged test cases. + +Figure E.2.2.2: iPerf Unidirectional delay CDF plot for GPON upstream scenario. The y-axis is 'CDF' (0.00 to 1.00) and the x-axis is '1-way delay (ms)' on a logarithmic scale (100 to 1000). The plot is divided into three sections: Partly Managed, Unmanaged, and Well Managed. Each section contains multiple curves representing different test cases (Gp2up, Gp3up, Gp4up, Gp5up, Gp6up, Gu1up, Gu2up, Gu3up, Gu4up, Gu5up, Gu6up, Gu7up, Gw1up, Gw2up, Gw3up, Gw4up, Gw5up, Gw6up). + +Figure E.2.2.2 – One-way iPerf delay CDF by direction and management type + + + +Figure E.2.2.3: iPerf Unidirectional BW Scenario: out.up. A line graph showing bandwidth (Mbps) over time (0 to 600 seconds) for three management scenarios: Well Managed, Partly Managed, and Unmanaged. The Y-axis ranges from 0 to 30 Mbps. The legend includes Gw1-Gw7 and Op1-Op6 for the first two scenarios, and Out1-Out7 for the third. The 'Well Managed' scenario shows stable bandwidth around 20-25 Mbps. The 'Partly Managed' and 'Unmanaged' scenarios show more fluctuation and lower peak bandwidths. + +Figure E.2.2.3 – One-way iPerf bandwidth by direction and management type + + + +Figure E.2.2.4: iPerf Unidirectional BW Scenario: out.up. A line graph showing bandwidth (Mbps) over time (0 to 600 seconds) for the 'Unmanaged' scenario. The Y-axis ranges from 0 to 30 Mbps. The legend includes Out1-Out7. The graph shows significant fluctuations in bandwidth, with peaks reaching approximately 25 Mbps and drops to near 0 Mbps. + +Figure E.2.2.4 – One-way iPerf bandwidth (unmanaged cases) + + + +Figure E.2.2.5: iPerf Unidirectional BW Scenario: out.up. A line graph showing bandwidth (Mbps) over time (0 to 600 seconds) for the 'Partly Managed' scenario. The Y-axis ranges from 0 to 30 Mbps. The legend includes Op1-Op6. The graph shows stable bandwidth around 20-25 Mbps, similar to the 'Well Managed' case. + +Figure E.2.2.5 – One-way iPerf bandwidth (partly managed cases) + + + +Figure E.2.2.6: iPerf Unidirectional BW Scenario: out.up. A line graph showing bandwidth (Mbps) over time (0 to 600 seconds) for the 'Well Managed' scenario. The Y-axis ranges from 0 to 25 Mbps. The legend includes Gw1-Gw7. The graph shows very stable bandwidth, maintaining a consistent level around 20-25 Mbps throughout the duration. + +Figure E.2.2.6 – One-way iPerf bandwidth (well managed cases) + + + +Figure E.2.2.7: One-way iPerf delay distribution (unmanaged cases). A violin plot showing delay distribution for seven hops (Gw1 to Gw7). The y-axis is logarithmic, ranging from 10 to 1000 ms. The x-axis is labeled 'Hop'. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.up (Min=11.03, Max=1306.51)'. + +Figure E.2.2.7 – One-way iPerf delay distribution (unmanaged cases) + + + +Figure E.2.2.8: One-way iPerf delay distribution (well managed cases). A violin plot showing delay distribution for six hops (Gp1 to Gp6). The y-axis is logarithmic, ranging from 10 to 1000 ms. The x-axis is labeled 'Hop'. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.up (Min=11.03, Max=1334.33)'. + +Figure E.2.2.8 – One-way iPerf delay distribution (well managed cases) + + + +Figure E.2.2.9: One-way iPerf delay distribution (partly managed cases). A violin plot showing delay distribution for eight hops (Gw1 to Gw8). The y-axis is logarithmic, ranging from 10 to 1000 ms. The x-axis is labeled 'Hop'. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.up (Min=11.03, Max=664.66)'. + +Figure E.2.2.9 – One-way iPerf delay distribution (partly managed cases) + + + +Figure E.2.2.10: Aggregate managed bandwidth (well and partly managed cases). A multi-panel plot showing bandwidth over time (0 to 600 seconds). The top-left panel shows 'Partly Managed' traffic with a green line. The top-right panel shows 'Well Managed' traffic with a pink line. The bottom-left panel shows aggregate bandwidth for 'Partly Managed' traffic with a green line. The bottom-right panel shows aggregate bandwidth for 'Well Managed' traffic with multiple colored lines. The y-axis for all panels is 'Bandwidth (Mbit)'. + +Figure E.2.2.10 – Aggregate managed bandwidth (well and partly managed cases) + +#### E.2.3 GPON downstream iPerf scenario + + + +This scatter plot shows the relationship between median bandwidth and median one-way delay for various network nodes in a GPON downstream scenario. The y-axis represents 'Median Bandwidth (Mbit)' on a logarithmic scale, and the x-axis represents 'Median 1-way Delay (ms)' on a linear scale. Data points are labeled with node names and categorized by management type: Partly Managed (red), Unmanaged (green), and Well Managed (blue). The legend indicates 'down' for the scenario. + +| Node | Management Type | Median 1-way Delay (ms) | Median Bandwidth (Mbit) | +|------|-----------------|-------------------------|-------------------------| +| Gw2 | Well Managed | ~80 | ~20 | +| Gu2 | Unmanaged | ~80 | ~18 | +| Gp2 | Partly Managed | ~80 | ~15 | +| Gu3 | Unmanaged | ~100 | ~12 | +| Gp3 | Partly Managed | ~100 | ~10 | +| Gw3 | Well Managed | ~100 | ~8 | +| Gw4 | Well Managed | ~120 | ~6 | +| Gw5 | Well Managed | ~130 | ~5 | +| Gp6 | Partly Managed | ~140 | ~4 | +| Gw7 | Well Managed | ~160 | ~3 | +| Gw8 | Well Managed | ~200 | ~2 | +| Gu5 | Unmanaged | ~220 | ~1.5 | +| Gp5 | Partly Managed | ~250 | ~1 | +| Gu6 | Unmanaged | ~230 | ~1.2 | +| Gu7 | Unmanaged | ~280 | ~0.8 | + +Scatter plot titled 'iPerf Bandwidth-Delay Scenario: out.dwn' showing Median Bandwidth (Mbit) vs. Median 1-way Delay (ms) for various network nodes. The plot is categorized into Partly Managed (red), Unmanaged (green), and Well Managed (blue). + +Figure E.2.3.1 – Test case median delay-bandwidth points + + + +This CDF plot shows the cumulative distribution function of one-way delay for different management types in a GPON downstream scenario. The y-axis represents the cumulative probability from 0.00 to 1.00, and the x-axis represents '1-way delay (ms)' on a logarithmic scale. The plot is divided into three sections: Partly Managed (red), Unmanaged (green), and Well Managed (blue). The legend lists various node identifiers (Idem) for each management type. + +| Management Type | Node Identifiers (Idem) | +|-----------------|----------------------------------------------------------------| +| Partly Managed | Gp1dwn, Gp5dwn, Gp6dwn | +| Unmanaged | Gu1dwn, Gu2dwn, Gu3dwn, Gu4dwn, Gu5dwn, Gu6dwn, Gu7dwn, Gu8dwn | +| Well Managed | Gw1dwn, Gw2dwn, Gw3dwn, Gw4dwn, Gw5dwn | + +CDF plot titled 'iPerf Unidirectional delay CDF Scenario: out.dwn' showing the cumulative distribution function of 1-way delay (ms) for different management types: Partly Managed, Unmanaged, and Well Managed. + +Figure E.2.3.2 – One-way iPerf delay CDF by direction and management type + + + +Figure E.2.3.3: iPerf Unidirectional BW Scenario: out.dwn. A multi-panel graph showing bandwidth usage over time (0 to 600 seconds) for three management scenarios: Well Managed, Partly Managed, and Unmanaged. The Y-axis represents Mbps (0 to 50). The X-axis represents time (0 to 600). The legend indicates flows: Gw1-Gw7 (orange), Op1-Op6 (green), and Out1-Out7 (purple). + +Figure E.2.3.3 – Test one-way iPerf bandwidth by direction and management type + + + +Figure E.2.3.4: iPerf Unidirectional BW Scenario: out.dwn. A graph showing bandwidth usage over time (0 to 600 seconds) for the Unmanaged scenario. The Y-axis represents Mbps (0 to 30). The X-axis represents time (0 to 600). The legend indicates flows: Out1-Out7 (purple). + +Figure E.2.3.4 – One-way iPerf bandwidth (unmanaged cases) + + + +Figure E.2.3.5: iPerf Unidirectional BW Scenario: out.dwn. A graph showing bandwidth usage over time (0 to 600 seconds) for the Partly Managed scenario. The Y-axis represents Mbps (0 to 30). The X-axis represents time (0 to 600). The legend indicates flows: Op1-Op6 (green). + +Figure E.2.3.5 – One-way iPerf bandwidth (partly managed cases) + + + +Figure E.2.3.6: iPerf Unidirectional BW Scenario: out.dwn. A graph showing bandwidth usage over time (0 to 600 seconds) for the Well Managed scenario. The Y-axis represents Mbps (0 to 50). The X-axis represents time (0 to 600). The legend indicates flows: Gw1-Gw7 (orange), Op1-Op6 (green), and Out1-Out7 (purple). + +Figure E.2.3.6 – One-way iPerf bandwidth (well managed cases) + + + +iPerf Unidirectional Log Delay (ms) +Scenario: out.dwn +(Min=11.02, Max=935.08) + +Gw1 Gw2 Gw3 Gw4 Gw5 Gw6 Gw7 + +1000 +100 +10 + +Unm + +down + +Box plot showing iPerf Unidirectional Log Delay (ms) for unmanaged cases across gateways Gw1 to Gw7. The y-axis is logarithmic from 10 to 1000. The x-axis labels are Gw1, Gw2, Gw3, Gw4, Gw5, Gw6, Gw7. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.dwn (Min=11.02, Max=935.08)'. + +Figure E.2.3.7 – One-way iPerf delay distribution (unmanaged cases) + + + +iPerf Unidirectional Log Delay (ms) +Scenario: out.dwn +(Min=11.02, Max=3366) + +Gp1 Gp2 Gp3 Gp4 Gp5 Gp6 + +1000 +100 +10 + +down + +Box plot showing iPerf Unidirectional Log Delay (ms) for well managed cases across gateways Gp1 to Gp6. The y-axis is logarithmic from 10 to 1000. The x-axis labels are Gp1, Gp2, Gp3, Gp4, Gp5, Gp6. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.dwn (Min=11.02, Max=3366)'. + +Figure E.2.3.8 – One-way iPerf delay distribution (well managed cases) + + + +iPerf Unidirectional Log Delay (ms) +Scenario: out.dwn +(Min=11.11, Max=816.19) + +Gw1 Gw2 Gw3 Gw4 Gw5 Gw6 Gw7 Gw8 + +1000 +100 +10 + +Unm + +down + +Box plot showing iPerf Unidirectional Log Delay (ms) for partly managed cases across gateways Gw1 to Gw8. The y-axis is logarithmic from 10 to 1000. The x-axis labels are Gw1, Gw2, Gw3, Gw4, Gw5, Gw6, Gw7, Gw8. The plot title is 'iPerf Unidirectional Log Delay (ms) Scenario: out.dwn (Min=11.11, Max=816.19)'. + +Figure E.2.3.9 – One-way iPerf delay distribution (partly managed cases) + + + +Managed Bandwidth +Scenario: out.dwn + +Partly Managed Well Managed + +0.024 +0.022 +0.020 +Bandwidth (Mbps) + +20 +15 +10 +5 +0 + +0 200 400 600 +time (sec) + +Op1-1 Op2-1 Op3-1 Op4-1 Op5-1 Op6-1 Gw1-1 Gw2-1 Gw3-1 Gw4-1 Gw5-1 Gw6-1 Gw7-1 Gw8-1 + +Line graph showing Aggregate managed bandwidth (Mbps) over time (sec) for well and partly managed cases. The y-axis ranges from 0 to 20 Mbps. The x-axis ranges from 0 to 600 seconds. The graph is split into 'Partly Managed' and 'Well Managed' sections. The legend includes Op1-1, Op2-1, Op3-1, Op4-1, Op5-1, Op6-1, Gw1-1, Gw2-1, Gw3-1, Gw4-1, Gw5-1, Gw6-1, Gw7-1, Gw8-1. + +Figure E.2.3.10 – Aggregate managed bandwidth (well and partly managed cases) + +# Annex F + +## Simulator output + +(This annex forms an integral part of this Recommendation.) + +Simulation results are found in the ./D and ./G directories of the model directory of the electronic attachment (Annex F). The simulation control scripts generate result files with the following naming conventions: + +- \$TECH – Technology (D=DSL, G=GPON); +- \$SC – iPerf Scenario: (out.bidi, out.dwn, out.up); +- \$TC – test case name (./tc/\$TC.param). These match the column headings in Tables 6, 7 and 8; +- \$FLOW – name of the managed monitor/flow in test case. These match the PCAP file names listed in Annex E. + +The results for each test case are found in a separate directory with the name of the test case. Each monitor specified in the test case represents a particular flow. Files are generated as shown in Table F.1: + +**Table F.1 – Simulator output file structure** + +| Directory or file name | Description | +|----------------------------------------|---------------------------------------------------------------| +| ./\$TECH/\$SC/cdf.csv | Summary iPerf CDF Table (Appendix E) | +| ./\$TECH/\$SC/PDF/\$TC.pdf | Directory containing .pdf files of merged plots of a scenario | +| ./\$TECH/\$SC/\$TC/ | Directory containing test case outputs. | +| | | +| ./\$TECH/\$SC/\$TC/\$FLOW.out | Output .out delay-loss schedule | +| ./\$TECH/\$SC/\$TC/\$FLOW-PDV.csv | Packet delay variation (PDV) file | +| ./\$TECH/\$SC/\$TC/\$TC-\$FLOW.png | Time series plot of .out file | +| ./\$TECH/\$SC/\$TC/\$TC-\$FLOW-PDV.png | PDV plot of delay-loss file | +| ./\$TECH/\$SC/\$TC/bw-{up,dwn}.csv | iPerf Delay/bandwidth data file | +| ./\$TECH/\$SC/PCAP/\$TC-modem.pcap.gz | Test case traffic file | + +Tables G.1 and G.2 summarize the simulation results of the managed flows for DSL and GPON respectively. Each row in the spreadsheet corresponds to a specific flow of a specific test case. Each flow results in the four \$FLOW files indicated above. + +Note that some of the output files, particularly the large ones, are compressed using the GZIP file format, and have an additional .gz suffix. + +# Annex G + +## Simulation results summary + +(This annex forms an integral part of this Recommendation.) + +Table G.1 and Table G.2 summarize the simulation results. Each row of the tables represent a single flow of a test case. The tables have been sorted by flow so that the behaviour can be observed across a flow type with increasing impairment severity. The coloration is an indication of the test profile (green – well managed, yellow – partially managed, red – unmanaged). Table G.3 summarizes simulation results (bandwidth, one-way delay and RTT) for iPerf flows for each test case. + +Description of the columns: + +- Profile + - W: well managed + - P: partially managed + - U: unmanaged +- Case + - test case name +- File + - output file name root (flow) +- n1 + - number of packets +- min + - min delay (ms) +- max + - max delay (ms) +- drop + - total number of packets lost +- seq + - number of packets lost in sequential events +- drop % + - total percentage of packets lost +- seq % + - percentage of packets lost sequentially +- max-min + - peak delay variation (ms) + +**Table G.1 – Simulation results summary DSL managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|-------|-------|------|-----|---------|---------|---------| +| Dp1t | SDTV1_Down | bidi | 113084 | 11.73 | 12.98 | 9 | 0 | 0.0080% | 0.0000% | 1.25 | +| | | dwn | 113085 | 11.73 | 13.02 | 8 | 0 | 0.0071% | 0.0000% | 1.28 | +| | | up | 113086 | 11.73 | 12.80 | 7 | 0 | 0.0062% | 0.0000% | 1.07 | +| | SDTV2_Down | bidi | 114887 | 11.73 | 13.31 | 12 | 0 | 0.0104% | 0.0000% | 1.58 | +| | | dwn | 114891 | 11.73 | 13.35 | 8 | 0 | 0.0070% | 0.0000% | 1.62 | +| | | up | 114890 | 11.73 | 13.13 | 9 | 0 | 0.0078% | 0.0000% | 1.40 | +| | VoIP1_Fwd | bidi | 20737 | 11.04 | 11.68 | 1 | 0 | 0.0048% | 0.0000% | 0.64 | +| | | dwn | 20738 | 11.04 | 11.69 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| | | up | 20738 | 11.04 | 11.64 | 0 | 0 | 0.0000% | 0.0000% | 0.59 | +| | VoIP1_Rev | bidi | 20736 | 11.21 | 15.30 | 0 | 0 | 0.0000% | 0.0000% | 4.09 | +| | | dwn | 20736 | 11.21 | 11.43 | 0 | 0 | 0.0000% | 0.0000% | 0.21 | +| | | up | 20736 | 11.21 | 15.22 | 0 | 0 | 0.0000% | 0.0000% | 4.01 | +| Dp2t | SDTV1_Down | bidi | 112961 | 26.89 | 42.65 | 129 | 0 | 0.1142% | 0.0000% | 15.76 | +| | | dwn | 112971 | 26.89 | 42.65 | 119 | 0 | 0.1053% | 0.0000% | 15.76 | +| | | up | 112949 | 26.89 | 42.65 | 141 | 0 | 0.1248% | 0.0000% | 15.76 | +| | SDTV2_Down | bidi | 114779 | 26.89 | 43.06 | 120 | 0 | 0.1045% | 0.0000% | 16.17 | +| | | dwn | 114755 | 26.89 | 43.06 | 144 | 0 | 0.1255% | 0.0000% | 16.17 | +| | | up | 114779 | 26.89 | 43.06 | 120 | 0 | 0.1045% | 0.0000% | 16.17 | +| | VoIP1_Fwd | bidi | 20737 | 26.05 | 26.87 | 0 | 0 | 0.0000% | 0.0000% | 0.82 | +| | | dwn | 20735 | 26.05 | 26.87 | 2 | 0 | 0.0096% | 0.0000% | 0.82 | +| | | up | 20735 | 26.05 | 26.80 | 2 | 0 | 0.0096% | 0.0000% | 0.74 | +| | VoIP1_Rev | bidi | 20733 | 26.41 | 34.46 | 2 | 0 | 0.0096% | 0.0000% | 8.05 | +| | | dwn | 20734 | 26.41 | 26.80 | 1 | 0 | 0.0048% | 0.0000% | 0.39 | +| | | up | 20733 | 26.41 | 34.42 | 2 | 0 | 0.0096% | 0.0000% | 8.01 | + +**Table G.1 – Simulation results summary DSL managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|-------|--------|------|-----|---------|---------|---------| +| Dp3t | SDTV1_Down | bidi | 112943 | 52.21 | 117.24 | 143 | 0 | 0.1266% | 0.0000% | 65.03 | +| | | dwn | 112956 | 52.21 | 117.18 | 130 | 0 | 0.1151% | 0.0000% | 64.97 | +| | | up | 112945 | 52.21 | 117.24 | 141 | 0 | 0.1248% | 0.0000% | 65.03 | +| | SDTV2_Down | bidi | 114756 | 52.21 | 117.26 | 143 | 0 | 0.1246% | 0.0000% | 65.05 | +| | | dwn | 114772 | 52.21 | 117.29 | 127 | 0 | 0.1107% | 0.0000% | 65.08 | +| | | up | 114777 | 52.21 | 117.26 | 122 | 0 | 0.1063% | 0.0000% | 65.05 | +| | VoIP1_Fwd | bidi | 20735 | 51.07 | 52.21 | 2 | 0 | 0.0096% | 0.0000% | 1.14 | +| | | dwn | 20737 | 51.07 | 52.22 | 0 | 0 | 0.0000% | 0.0000% | 1.14 | +| | | up | 20735 | 51.07 | 52.11 | 2 | 0 | 0.0096% | 0.0000% | 1.04 | +| | VoIP1_Rev | bidi | 20734 | 51.41 | 59.49 | 0 | 0 | 0.0000% | 0.0000% | 8.08 | +| | | dwn | 20733 | 51.41 | 51.79 | 1 | 0 | 0.0048% | 0.0000% | 0.38 | +| | | up | 20732 | 51.41 | 59.42 | 2 | 0 | 0.0096% | 0.0000% | 8.01 | +| Dp4t | SDTV1_Down | bidi | 111826 | 78.14 | 208.98 | 1255 | 59 | 1.1223% | 0.0528% | 130.83 | +| | | dwn | 111803 | 78.14 | 208.14 | 1278 | 63 | 1.1431% | 0.0563% | 129.99 | +| | | up | 111809 | 78.14 | 208.99 | 1272 | 37 | 1.1377% | 0.0331% | 130.85 | +| | SDTV2_Down | bidi | 113574 | 78.14 | 208.98 | 1324 | 79 | 1.1658% | 0.0696% | 130.84 | +| | | dwn | 113590 | 78.14 | 208.89 | 1308 | 58 | 1.1515% | 0.0511% | 130.75 | +| | | up | 113541 | 78.14 | 208.99 | 1357 | 86 | 1.1952% | 0.0757% | 130.84 | +| | VoIP1_Fwd | bidi | 20720 | 76.12 | 78.25 | 16 | 0 | 0.0772% | 0.0000% | 2.13 | +| | | dwn | 20730 | 76.12 | 78.25 | 6 | 0 | 0.0289% | 0.0000% | 2.13 | +| | | up | 20723 | 76.12 | 78.05 | 13 | 0 | 0.0627% | 0.0000% | 1.93 | +| | VoIP1_Rev | bidi | 20717 | 76.60 | 88.73 | 16 | 0 | 0.0772% | 0.0000% | 12.13 | +| | | dwn | 20722 | 76.60 | 77.18 | 11 | 0 | 0.0531% | 0.0000% | 0.58 | +| | | up | 20721 | 76.60 | 88.72 | 12 | 0 | 0.0579% | 0.0000% | 12.12 | + +**Table G.1 – Simulation results summary DSL managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|--------|--------|------|-----|---------|---------|---------| +| Dp5t | SDTV2_Down | bidi | 113320 | 104.98 | 367.44 | 1578 | 169 | 1.3925% | 0.1491% | 262.46 | +| | | dwn | 113387 | 104.98 | 367.43 | 1511 | 168 | 1.3326% | 0.1482% | 262.46 | +| | | up | 113360 | 104.98 | 367.44 | 1538 | 171 | 1.3567% | 0.1508% | 262.46 | +| | VoIP1_Fwd | bidi | 20727 | 101.22 | 105.27 | 8 | 0 | 0.0386% | 0.0000% | 4.05 | +| | | dwn | 20723 | 101.22 | 105.29 | 12 | 0 | 0.0579% | 0.0000% | 4.07 | +| | | up | 20720 | 101.22 | 104.96 | 15 | 0 | 0.0724% | 0.0000% | 3.74 | +| | VoIP1_Rev | bidi | 20720 | 101.60 | 113.72 | 13 | 0 | 0.0627% | 0.0000% | 12.12 | +| | | dwn | 20719 | 101.60 | 102.18 | 14 | 0 | 0.0676% | 0.0000% | 0.58 | +| | | up | 20722 | 101.60 | 113.73 | 11 | 0 | 0.0531% | 0.0000% | 12.13 | +| Dp6t | SDTV1_Down | bidi | 111819 | 203.19 | 334.00 | 1239 | 39 | 1.1080% | 0.0349% | 130.81 | +| | | dwn | 111778 | 203.19 | 333.18 | 1280 | 46 | 1.1451% | 0.0412% | 129.99 | +| | | up | 111762 | 203.19 | 334.03 | 1296 | 39 | 1.1596% | 0.0349% | 130.85 | +| | SDTV2_Down | bidi | 113562 | 203.19 | 334.03 | 1335 | 80 | 1.1756% | 0.0704% | 130.85 | +| | | dwn | 113591 | 203.19 | 333.94 | 1306 | 56 | 1.1497% | 0.0493% | 130.75 | +| | | up | 113560 | 203.19 | 334.03 | 1337 | 80 | 1.1774% | 0.0704% | 130.84 | +| | VoIP1_Fwd | bidi | 20721 | 201.12 | 203.30 | 11 | 0 | 0.0531% | 0.0000% | 2.18 | +| | | dwn | 20720 | 201.12 | 203.30 | 12 | 0 | 0.0579% | 0.0000% | 2.18 | +| | | up | 20717 | 201.12 | 203.09 | 15 | 0 | 0.0724% | 0.0000% | 1.97 | +| | VoIP1_Rev | bidi | 20717 | 201.60 | 213.73 | 12 | 0 | 0.0579% | 0.0000% | 12.13 | +| | | dwn | 20715 | 201.60 | 202.18 | 14 | 0 | 0.0676% | 0.0000% | 0.58 | +| | | up | 20719 | 201.60 | 213.73 | 10 | 0 | 0.0483% | 0.0000% | 12.13 | +| Dw1t | HDTV1_Down | bidi | 451520 | 11.61 | 12.98 | 42 | 0 | 0.0093% | 0.0000% | 1.37 | +| | | dwn | 451522 | 11.61 | 13.27 | 40 | 0 | 0.0089% | 0.0000% | 1.66 | +| | | up | 451523 | 11.61 | 12.98 | 39 | 0 | 0.0086% | 0.0000% | 1.37 | +| | VoIP1_Fwd | bidi | 20738 | 11.04 | 11.62 | 0 | 0 | 0.0000% | 0.0000% | 0.58 | + +**Table G.1 – Simulation results summary DSL managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|-------|-------|------|-----|---------|---------|---------| +| | | dwn | 20738 | 11.04 | 11.61 | 0 | 0 | 0.0000% | 0.0000% | 0.58 | +| | | up | 20737 | 11.04 | 11.62 | 1 | 0 | 0.0048% | 0.0000% | 0.58 | +| | VoIP1_Rev | bidi | 20736 | 11.21 | 15.27 | 0 | 0 | 0.0000% | 0.0000% | 4.06 | +| | | dwn | 20736 | 11.21 | 11.42 | 0 | 0 | 0.0000% | 0.0000% | 0.21 | +| | | up | 20736 | 11.21 | 15.22 | 0 | 0 | 0.0000% | 0.0000% | 4.01 | +| Dw2t | HDTV1_Down | bidi | 451520 | 26.62 | 28.52 | 31 | 0 | 0.0069% | 0.0000% | 1.90 | +| | | dwn | 451497 | 26.62 | 28.53 | 54 | 0 | 0.0120% | 0.0000% | 1.91 | +| | | up | 451519 | 26.62 | 28.32 | 32 | 0 | 0.0071% | 0.0000% | 1.70 | +| | SDTV1_Down | bidi | 113082 | 26.62 | 28.25 | 8 | 0 | 0.0071% | 0.0000% | 1.63 | +| | | dwn | 113081 | 26.62 | 28.26 | 9 | 0 | 0.0080% | 0.0000% | 1.64 | +| | | up | 113074 | 26.62 | 28.04 | 16 | 0 | 0.0142% | 0.0000% | 1.43 | +| | VoIP1_Fwd | bidi | 20737 | 26.04 | 26.63 | 0 | 0 | 0.0000% | 0.0000% | 0.59 | +| | | dwn | 20737 | 26.04 | 26.63 | 0 | 0 | 0.0000% | 0.0000% | 0.59 | +| | | up | 20736 | 26.04 | 26.63 | 1 | 0 | 0.0048% | 0.0000% | 0.59 | +| | VoIP1_Rev | bidi | 20735 | 26.21 | 30.39 | 0 | 0 | 0.0000% | 0.0000% | 4.17 | +| | | dwn | 20735 | 26.21 | 26.42 | 0 | 0 | 0.0000% | 0.0000% | 0.21 | +| | | up | 20735 | 26.21 | 30.34 | 0 | 0 | 0.0000% | 0.0000% | 4.13 | +| Dw3t | HDTV1_Down | bidi | 451470 | 51.63 | 75.32 | 63 | 15 | 0.0140% | 0.0033% | 23.69 | +| | | dwn | 451471 | 51.63 | 75.32 | 62 | 13 | 0.0137% | 0.0029% | 23.69 | +| | | up | 451458 | 51.63 | 75.32 | 75 | 15 | 0.0166% | 0.0033% | 23.69 | +| | HDTV2_Down | bidi | 391370 | 51.37 | 75.35 | 83 | 10 | 0.0212% | 0.0026% | 23.97 | +| | | dwn | 391374 | 51.37 | 75.35 | 79 | 14 | 0.0202% | 0.0036% | 23.98 | +| | | up | 391386 | 51.37 | 75.35 | 67 | 10 | 0.0171% | 0.0026% | 23.97 | +| | | bidi | 20737 | 51.04 | 51.64 | 0 | 0 | 0.0000% | 0.0000% | 0.60 | +| | VoIP1_Fwd | dwn | 20737 | 51.04 | 51.64 | 0 | 0 | 0.0000% | 0.0000% | 0.60 | + +**Table G.1 – Simulation results summary DSL managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|-------|--------|------|-----|---------|---------|---------| +| | VoIP1_Rev | up | 20737 | 51.04 | 51.64 | 0 | 0 | 0.0000% | 0.0000% | 0.60 | +| | | bidi | 20734 | 51.21 | 55.29 | 0 | 0 | 0.0000% | 0.0000% | 4.08 | +| | | dwn | 20734 | 51.21 | 51.47 | 0 | 0 | 0.0000% | 0.0000% | 0.26 | +| | | up | 20734 | 51.21 | 55.22 | 0 | 0 | 0.0000% | 0.0000% | 4.01 | +| Dw4t | HDTV1_Down | bidi | 451474 | 76.80 | 103.61 | 41 | 0 | 0.0091% | 0.0000% | 26.81 | +| | | dwn | 451469 | 76.80 | 103.45 | 46 | 0 | 0.0102% | 0.0000% | 26.65 | +| | | up | 451470 | 76.80 | 103.25 | 45 | 0 | 0.0100% | 0.0000% | 26.44 | +| | SDTV1_Down | bidi | 113065 | 76.80 | 103.30 | 16 | 0 | 0.0142% | 0.0000% | 26.49 | +| | | dwn | 113071 | 76.80 | 103.14 | 10 | 0 | 0.0088% | 0.0000% | 26.34 | +| | | up | 113073 | 76.80 | 102.93 | 8 | 0 | 0.0071% | 0.0000% | 26.13 | +| | SDTV2_Down | bidi | 114890 | 76.80 | 103.68 | 8 | 0 | 0.0070% | 0.0000% | 26.88 | +| | | dwn | 114890 | 76.80 | 103.52 | 8 | 0 | 0.0070% | 0.0000% | 26.72 | +| | | up | 114891 | 76.80 | 103.32 | 7 | 0 | 0.0061% | 0.0000% | 26.51 | +| | VoIP1_Fwd | bidi | 20736 | 76.05 | 76.81 | 0 | 0 | 0.0000% | 0.0000% | 0.76 | +| | | dwn | 20736 | 76.05 | 76.81 | 0 | 0 | 0.0000% | 0.0000% | 0.76 | +| | | up | 20736 | 76.05 | 76.81 | 0 | 0 | 0.0000% | 0.0000% | 0.76 | +| | VoIP1_Rev | bidi | 20733 | 76.31 | 82.40 | 0 | 0 | 0.0000% | 0.0000% | 6.09 | +| | | dwn | 20733 | 76.31 | 76.68 | 0 | 0 | 0.0000% | 0.0000% | 0.37 | +| | | up | 20733 | 76.31 | 82.32 | 0 | 0 | 0.0000% | 0.0000% | 6.01 | +| Dw5t | HDTV1_Down | bidi | 451004 | 87.00 | 94.30 | 504 | 0 | 0.1118% | 0.0000% | 7.30 | +| | | dwn | 450974 | 87.00 | 93.60 | 534 | 0 | 0.1184% | 0.0000% | 6.60 | +| | | up | 451000 | 87.00 | 93.60 | 508 | 0 | 0.1126% | 0.0000% | 6.60 | +| | SDTV1_Down | bidi | 112944 | 87.00 | 93.33 | 135 | 0 | 0.1195% | 0.0000% | 6.33 | +| | | dwn | 112973 | 87.00 | 92.62 | 106 | 0 | 0.0938% | 0.0000% | 5.62 | +| | | up | 112947 | 87.00 | 92.62 | 132 | 0 | 0.1169% | 0.0000% | 5.62 | + +**Table G.1 – Simulation results summary DSL managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|--------|--------|------|-----|---------|---------|---------| +| | VoIP1_Fwd | bidi | 20735 | 86.06 | 87.01 | 0 | 0 | 0.0000% | 0.0000% | 0.95 | +| | | dwn | 20735 | 86.06 | 87.01 | 0 | 0 | 0.0000% | 0.0000% | 0.95 | +| | | up | 20734 | 86.06 | 87.01 | 1 | 0 | 0.0048% | 0.0000% | 0.95 | +| | VoIP1_Rev | bidi | 20731 | 86.60 | 98.68 | 2 | 0 | 0.0096% | 0.0000% | 12.08 | +| | | dwn | 20730 | 86.60 | 87.18 | 3 | 0 | 0.0145% | 0.0000% | 0.58 | +| | | up | 20732 | 86.60 | 98.62 | 1 | 0 | 0.0048% | 0.0000% | 12.02 | +| Dw6t | HDTV1_Down | bidi | 450970 | 102.01 | 150.97 | 527 | 8 | 0.1169% | 0.0018% | 48.96 | +| | | dwn | 450996 | 102.01 | 150.94 | 501 | 14 | 0.1111% | 0.0031% | 48.93 | +| | | up | 450997 | 102.01 | 150.94 | 500 | 12 | 0.1109% | 0.0027% | 48.93 | +| | SDTV1_Down | bidi | 112945 | 102.01 | 150.63 | 131 | 5 | 0.1160% | 0.0044% | 48.62 | +| | | dwn | 112930 | 102.01 | 150.91 | 146 | 6 | 0.1293% | 0.0053% | 48.89 | +| | | up | 112940 | 102.01 | 150.91 | 136 | 6 | 0.1204% | 0.0053% | 48.89 | +| | SDTV2_Down | bidi | 114754 | 102.01 | 150.95 | 144 | 8 | 0.1255% | 0.0070% | 48.94 | +| | | dwn | 114720 | 102.01 | 150.96 | 178 | 8 | 0.1552% | 0.0070% | 48.94 | +| | | up | 114739 | 102.01 | 150.96 | 159 | 6 | 0.1386% | 0.0052% | 48.94 | +| | VoIP1_Fwd | bidi | 20735 | 101.06 | 102.02 | 0 | 0 | 0.0000% | 0.0000% | 0.96 | +| | | dwn | 20735 | 101.06 | 102.02 | 0 | 0 | 0.0000% | 0.0000% | 0.96 | +| | | up | 20734 | 101.06 | 102.02 | 1 | 0 | 0.0048% | 0.0000% | 0.96 | +| | VoIP1_Rev | bidi | 20729 | 101.60 | 113.62 | 4 | 0 | 0.0193% | 0.0000% | 12.02 | +| | | dwn | 20731 | 101.60 | 102.25 | 2 | 0 | 0.0096% | 0.0000% | 0.65 | +| | | up | 20731 | 101.60 | 113.62 | 2 | 0 | 0.0096% | 0.0000% | 12.02 | +| Dw7t | HDTV1_Down | bidi | 450958 | 127.02 | 175.95 | 521 | 12 | 0.1155% | 0.0027% | 48.93 | +| | | dwn | 450955 | 127.02 | 175.95 | 524 | 12 | 0.1162% | 0.0027% | 48.93 | +| | | up | 450962 | 127.02 | 175.95 | 517 | 12 | 0.1146% | 0.0027% | 48.93 | +| | SDTV1_Down | bidi | 112938 | 127.02 | 175.92 | 134 | 6 | 0.1186% | 0.0053% | 48.89 | + +**Table G.1 – Simulation results summary DSL managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|--------|--------|------|-----|---------|---------|---------| +| | | dwn | 112940 | 127.02 | 175.92 | 132 | 6 | 0.1169% | 0.0053% | 48.89 | +| | | up | 112933 | 127.02 | 175.92 | 139 | 6 | 0.1231% | 0.0053% | 48.89 | +| | SDTV2_Down | bidi | 114740 | 127.02 | 175.97 | 158 | 8 | 0.1377% | 0.0070% | 48.94 | +| | | dwn | 114732 | 127.02 | 175.97 | 166 | 6 | 0.1447% | 0.0052% | 48.94 | +| | | up | 114755 | 127.02 | 175.97 | 143 | 6 | 0.1246% | 0.0052% | 48.94 | +| | VoIP1_Fwd | bidi | 20733 | 126.06 | 127.03 | 1 | 0 | 0.0048% | 0.0000% | 0.97 | +| | | dwn | 20734 | 126.06 | 127.03 | 0 | 0 | 0.0000% | 0.0000% | 0.97 | +| | | up | 20732 | 126.06 | 127.03 | 2 | 0 | 0.0096% | 0.0000% | 0.97 | +| | VoIP1_Rev | bidi | 20729 | 126.60 | 138.64 | 3 | 0 | 0.0145% | 0.0000% | 12.04 | +| | | dwn | 20731 | 126.60 | 127.24 | 1 | 0 | 0.0048% | 0.0000% | 0.64 | +| | | up | 20731 | 126.60 | 138.62 | 1 | 0 | 0.0048% | 0.0000% | 12.01 | +| Dw8t | HDTV1_Down | bidi | 450926 | 152.44 | 164.40 | 533 | 2 | 0.1182% | 0.0004% | 11.96 | +| | | dwn | 450950 | 152.44 | 164.56 | 509 | 0 | 0.1129% | 0.0000% | 12.12 | +| | | up | 450922 | 152.44 | 163.71 | 537 | 0 | 0.1191% | 0.0000% | 11.27 | +| | VoIP1_Fwd | bidi | 20732 | 151.08 | 152.45 | 1 | 0 | 0.0048% | 0.0000% | 1.37 | +| | | dwn | 20733 | 151.08 | 152.46 | 0 | 0 | 0.0000% | 0.0000% | 1.38 | +| | | up | 20733 | 151.08 | 152.45 | 0 | 0 | 0.0000% | 0.0000% | 1.37 | +| | VoIP1_Rev | bidi | 20731 | 151.60 | 163.62 | 0 | 0 | 0.0000% | 0.0000% | 12.01 | +| | | dwn | 20729 | 151.60 | 152.47 | 2 | 0 | 0.0096% | 0.0000% | 0.86 | +| | | up | 20727 | 151.60 | 163.62 | 4 | 0 | 0.0193% | 0.0000% | 12.02 | + +**Table G.2 – Simulation results summary GPON managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|-------|-------|------|-----|---------|---------|---------| +| Gp1t | SDTV1_Down | bidi | 113093 | 11.59 | 12.24 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| | | dwn | 113093 | 11.59 | 12.24 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| | | up | 113093 | 11.59 | 11.91 | 0 | 0 | 0.0000% | 0.0000% | 0.32 | +| | SDTV2_Down | bidi | 114899 | 11.59 | 12.25 | 0 | 0 | 0.0000% | 0.0000% | 0.66 | +| | | dwn | 114899 | 11.59 | 12.24 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| | | up | 114899 | 11.59 | 11.91 | 0 | 0 | 0.0000% | 0.0000% | 0.32 | +| | VoIP1_Fwd | bidi | 20738 | 11.04 | 11.53 | 0 | 0 | 0.0000% | 0.0000% | 0.50 | +| | | dwn | 20738 | 11.04 | 11.53 | 0 | 0 | 0.0000% | 0.0000% | 0.50 | +| | | up | 20738 | 11.04 | 11.49 | 0 | 0 | 0.0000% | 0.0000% | 0.46 | +| | VoIP1_Rev | bidi | 20736 | 11.04 | 11.53 | 0 | 0 | 0.0000% | 0.0000% | 0.49 | +| | | dwn | 20736 | 11.04 | 11.05 | 0 | 0 | 0.0000% | 0.0000% | 0.02 | +| | | up | 20736 | 11.04 | 11.52 | 0 | 0 | 0.0000% | 0.0000% | 0.49 | +| Gp2t | SDTV1_Down | bidi | 113090 | 26.60 | 27.25 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| | | dwn | 113090 | 26.60 | 27.25 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| | | up | 113090 | 26.60 | 26.92 | 0 | 0 | 0.0000% | 0.0000% | 0.32 | +| | SDTV2_Down | bidi | 114899 | 26.60 | 27.24 | 0 | 0 | 0.0000% | 0.0000% | 0.64 | +| | | dwn | 114899 | 26.60 | 27.25 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| | | up | 114899 | 26.60 | 26.92 | 0 | 0 | 0.0000% | 0.0000% | 0.32 | +| | VoIP1_Fwd | bidi | 20737 | 26.04 | 26.54 | 0 | 0 | 0.0000% | 0.0000% | 0.50 | +| | | dwn | 20737 | 26.04 | 26.54 | 0 | 0 | 0.0000% | 0.0000% | 0.51 | +| | | up | 20737 | 26.04 | 26.51 | 0 | 0 | 0.0000% | 0.0000% | 0.47 | +| | VoIP1_Rev | bidi | 20735 | 26.06 | 26.99 | 0 | 0 | 0.0000% | 0.0000% | 0.93 | +| | | dwn | 20735 | 26.06 | 26.10 | 0 | 0 | 0.0000% | 0.0000% | 0.04 | +| | | up | 20735 | 26.06 | 26.99 | 0 | 0 | 0.0000% | 0.0000% | 0.93 | + +**Table G.2 – Simulation results summary GPON managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|-------|--------|------|-----|---------|---------|---------| +| Gp3t | SDTV1_Down | bidi | 113086 | 51.73 | 52.65 | 0 | 0 | 0.0000% | 0.0000% | 0.91 | +| | | dwn | 113086 | 51.73 | 52.65 | 0 | 0 | 0.0000% | 0.0000% | 0.91 | +| | | up | 113086 | 51.73 | 52.19 | 0 | 0 | 0.0000% | 0.0000% | 0.45 | +| | SDTV2_Down | bidi | 114899 | 51.73 | 52.65 | 0 | 0 | 0.0000% | 0.0000% | 0.91 | +| | | dwn | 114899 | 51.73 | 52.65 | 0 | 0 | 0.0000% | 0.0000% | 0.91 | +| | | up | 114899 | 51.73 | 52.19 | 0 | 0 | 0.0000% | 0.0000% | 0.46 | +| | VoIP1_Fwd | bidi | 20737 | 51.05 | 51.69 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| | | dwn | 20737 | 51.05 | 51.69 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| | | up | 20737 | 51.05 | 51.64 | 0 | 0 | 0.0000% | 0.0000% | 0.60 | +| | VoIP1_Rev | bidi | 20734 | 51.05 | 51.69 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| | | dwn | 20734 | 51.05 | 51.07 | 0 | 0 | 0.0000% | 0.0000% | 0.02 | +| | | up | 20734 | 51.05 | 51.69 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| Gp4t | SDTV1_Down | bidi | 113081 | 77.06 | 110.41 | 0 | 0 | 0.0000% | 0.0000% | 33.35 | +| | | dwn | 113081 | 77.06 | 110.73 | 0 | 0 | 0.0000% | 0.0000% | 33.67 | +| | | up | 113081 | 77.06 | 110.21 | 0 | 0 | 0.0000% | 0.0000% | 33.15 | +| | SDTV2_Down | bidi | 114895 | 77.06 | 110.54 | 3 | 0 | 0.0026% | 0.0000% | 33.48 | +| | | dwn | 114895 | 77.06 | 110.86 | 3 | 0 | 0.0026% | 0.0000% | 33.80 | +| | | up | 114895 | 77.06 | 110.34 | 3 | 0 | 0.0026% | 0.0000% | 33.28 | +| | VoIP1_Fwd | bidi | 20736 | 76.06 | 77.05 | 0 | 0 | 0.0000% | 0.0000% | 0.99 | +| | | dwn | 20736 | 76.06 | 77.05 | 0 | 0 | 0.0000% | 0.0000% | 0.99 | +| | | up | 20736 | 76.06 | 76.96 | 0 | 0 | 0.0000% | 0.0000% | 0.90 | +| | VoIP1_Rev | bidi | 20733 | 76.14 | 78.65 | 0 | 0 | 0.0000% | 0.0000% | 2.51 | +| | | dwn | 20733 | 76.14 | 76.26 | 0 | 0 | 0.0000% | 0.0000% | 0.12 | +| | | up | 20733 | 76.14 | 78.62 | 0 | 0 | 0.0000% | 0.0000% | 2.48 | + +**Table G.2 – Simulation results summary GPON managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|--------|--------|------|-----|---------|---------|---------| +| Gp5t | SDTV2_Down | bidi | 114833 | 103.53 | 260.64 | 65 | 42 | 0.0566% | 0.0366% | 157.11 | +| | | dwn | 114835 | 103.53 | 260.53 | 63 | 42 | 0.0549% | 0.0366% | 157.01 | +| | | up | 114836 | 103.53 | 260.54 | 62 | 42 | 0.0540% | 0.0366% | 157.01 | +| | VoIP1_Fwd | bidi | 20735 | 101.14 | 103.67 | 0 | 0 | 0.0000% | 0.0000% | 2.53 | +| | | dwn | 20735 | 101.14 | 103.67 | 0 | 0 | 0.0000% | 0.0000% | 2.52 | +| | | up | 20735 | 101.14 | 103.44 | 0 | 0 | 0.0000% | 0.0000% | 2.30 | +| | VoIP1_Rev | bidi | 20733 | 101.31 | 107.43 | 0 | 0 | 0.0000% | 0.0000% | 6.11 | +| | | dwn | 20733 | 101.31 | 101.64 | 0 | 0 | 0.0000% | 0.0000% | 0.33 | +| | | up | 20733 | 101.31 | 107.48 | 0 | 0 | 0.0000% | 0.0000% | 6.16 | +| Gp6t | SDTV1_Down | bidi | 113054 | 202.10 | 235.25 | 4 | 0 | 0.0035% | 0.0000% | 33.15 | +| | | dwn | 113055 | 202.10 | 235.25 | 3 | 0 | 0.0027% | 0.0000% | 33.15 | +| | | up | 113058 | 202.10 | 235.25 | 0 | 0 | 0.0000% | 0.0000% | 33.15 | +| | SDTV2_Down | bidi | 114895 | 202.10 | 235.38 | 2 | 0 | 0.0017% | 0.0000% | 33.28 | +| | | dwn | 114896 | 202.10 | 235.38 | 1 | 0 | 0.0009% | 0.0000% | 33.28 | +| | | up | 114896 | 202.10 | 235.38 | 1 | 0 | 0.0009% | 0.0000% | 33.28 | +| | VoIP1_Fwd | bidi | 20732 | 201.07 | 202.10 | 0 | 0 | 0.0000% | 0.0000% | 1.03 | +| | | dwn | 20732 | 201.07 | 202.10 | 0 | 0 | 0.0000% | 0.0000% | 1.03 | +| | | up | 20732 | 201.07 | 202.01 | 0 | 0 | 0.0000% | 0.0000% | 0.94 | +| | VoIP1_Rev | bidi | 20729 | 201.14 | 203.69 | 0 | 0 | 0.0000% | 0.0000% | 2.54 | +| | | dwn | 20729 | 201.14 | 201.31 | 0 | 0 | 0.0000% | 0.0000% | 0.17 | +| | | up | 20729 | 201.14 | 203.69 | 0 | 0 | 0.0000% | 0.0000% | 2.55 | +| Gw1t | HDTV1_Down | bidi | 451561 | 11.50 | 11.93 | 1 | 0 | 0.0002% | 0.0000% | 0.43 | +| | | dwn | 451562 | 11.50 | 11.90 | 0 | 0 | 0.0000% | 0.0000% | 0.40 | +| | | up | 451562 | 11.50 | 11.71 | 0 | 0 | 0.0000% | 0.0000% | 0.22 | + +**Table G.2 – Simulation results summary GPON managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|-------|-------|------|-----|---------|---------|---------| +| | VoIP1_Fwd | bidi | 20738 | 11.03 | 11.50 | 0 | 0 | 0.0000% | 0.0000% | 0.47 | +| | | dwn | 20738 | 11.03 | 11.50 | 0 | 0 | 0.0000% | 0.0000% | 0.47 | +| | | up | 20738 | 11.03 | 11.50 | 0 | 0 | 0.0000% | 0.0000% | 0.47 | +| | VoIP1_Rev | bidi | 20736 | 11.04 | 11.67 | 0 | 0 | 0.0000% | 0.0000% | 0.62 | +| | | dwn | 20736 | 11.04 | 11.07 | 0 | 0 | 0.0000% | 0.0000% | 0.02 | +| | | up | 20736 | 11.04 | 11.66 | 0 | 0 | 0.0000% | 0.0000% | 0.62 | +| Gw2t | HDTV1_Down | bidi | 451552 | 26.51 | 26.97 | 0 | 0 | 0.0000% | 0.0000% | 0.46 | +| | | dwn | 451552 | 26.51 | 26.97 | 0 | 0 | 0.0000% | 0.0000% | 0.46 | +| | | up | 451552 | 26.51 | 26.73 | 0 | 0 | 0.0000% | 0.0000% | 0.23 | +| | SDTV1_Down | bidi | 113090 | 26.51 | 26.96 | 0 | 0 | 0.0000% | 0.0000% | 0.45 | +| | | dwn | 113090 | 26.51 | 26.97 | 0 | 0 | 0.0000% | 0.0000% | 0.47 | +| | | up | 113090 | 26.51 | 26.73 | 0 | 0 | 0.0000% | 0.0000% | 0.22 | +| | VoIP1_Fwd | bidi | 20737 | 26.03 | 26.51 | 0 | 0 | 0.0000% | 0.0000% | 0.48 | +| | | dwn | 20737 | 26.03 | 26.51 | 0 | 0 | 0.0000% | 0.0000% | 0.48 | +| | | up | 20737 | 26.03 | 26.51 | 0 | 0 | 0.0000% | 0.0000% | 0.48 | +| | VoIP1_Rev | bidi | 20735 | 26.04 | 26.68 | 0 | 0 | 0.0000% | 0.0000% | 0.63 | +| | | dwn | 20735 | 26.04 | 26.07 | 0 | 0 | 0.0000% | 0.0000% | 0.02 | +| | | up | 20735 | 26.04 | 26.68 | 0 | 0 | 0.0000% | 0.0000% | 0.63 | +| Gw3t | HDTV1_Down | bidi | 451529 | 51.61 | 73.98 | 4 | 2 | 0.0009% | 0.0004% | 22.37 | +| | | dwn | 451526 | 51.61 | 73.96 | 7 | 7 | 0.0016% | 0.0016% | 22.35 | +| | | up | 451530 | 51.61 | 73.91 | 3 | 0 | 0.0007% | 0.0000% | 22.30 | +| | HDTV2_Down | bidi | 391440 | 51.36 | 73.97 | 13 | 4 | 0.0033% | 0.0010% | 22.61 | +| | | dwn | 391442 | 51.36 | 73.97 | 11 | 0 | 0.0028% | 0.0000% | 22.61 | +| | | up | 391440 | 51.36 | 73.96 | 13 | 4 | 0.0033% | 0.0010% | 22.60 | + +**Table G.2 – Simulation results summary GPON managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|------|------------|------|--------|-------|-------|------|-----|---------|---------|---------| +| | VoIP1_Fwd | bidi | 20737 | 51.04 | 51.62 | 0 | 0 | 0.0000% | 0.0000% | 0.58 | +| | | dwn | 20737 | 51.04 | 51.62 | 0 | 0 | 0.0000% | 0.0000% | 0.58 | +| | | up | 20737 | 51.04 | 51.62 | 0 | 0 | 0.0000% | 0.0000% | 0.58 | +| | VoIP1_Rev | bidi | 20734 | 51.05 | 51.69 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| | | dwn | 20734 | 51.05 | 51.07 | 0 | 0 | 0.0000% | 0.0000% | 0.02 | +| | | up | 20734 | 51.05 | 51.69 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| Gw4t | HDTV1_Down | bidi | 451514 | 76.62 | 78.23 | 1 | 0 | 0.0002% | 0.0000% | 1.61 | +| | | dwn | 451515 | 76.62 | 78.26 | 0 | 0 | 0.0000% | 0.0000% | 1.63 | +| | | up | 451515 | 76.62 | 78.11 | 0 | 0 | 0.0000% | 0.0000% | 1.49 | +| | SDTV1_Down | bidi | 113081 | 76.62 | 78.00 | 0 | 0 | 0.0000% | 0.0000% | 1.38 | +| | | dwn | 113081 | 76.62 | 77.82 | 0 | 0 | 0.0000% | 0.0000% | 1.20 | +| | | up | 113081 | 76.62 | 77.82 | 0 | 0 | 0.0000% | 0.0000% | 1.20 | +| | SDTV2_Down | bidi | 114898 | 76.62 | 78.11 | 0 | 0 | 0.0000% | 0.0000% | 1.49 | +| | | dwn | 114898 | 76.62 | 77.91 | 0 | 0 | 0.0000% | 0.0000% | 1.29 | +| | | up | 114898 | 76.62 | 77.81 | 0 | 0 | 0.0000% | 0.0000% | 1.19 | +| | VoIP1_Fwd | bidi | 20736 | 76.04 | 76.63 | 0 | 0 | 0.0000% | 0.0000% | 0.59 | +| | | dwn | 20736 | 76.04 | 76.63 | 0 | 0 | 0.0000% | 0.0000% | 0.59 | +| | | up | 20736 | 76.04 | 76.63 | 0 | 0 | 0.0000% | 0.0000% | 0.59 | +| | VoIP1_Rev | bidi | 20733 | 76.05 | 76.70 | 0 | 0 | 0.0000% | 0.0000% | 0.66 | +| | | dwn | 20733 | 76.05 | 76.07 | 0 | 0 | 0.0000% | 0.0000% | 0.02 | +| | | up | 20733 | 76.05 | 76.70 | 0 | 0 | 0.0000% | 0.0000% | 0.65 | +| Gw5t | HDTV1_Down | bidi | 451508 | 86.76 | 90.35 | 0 | 0 | 0.0000% | 0.0000% | 3.60 | +| | | dwn | 451508 | 86.76 | 90.38 | 0 | 0 | 0.0000% | 0.0000% | 3.62 | +| | | up | 451508 | 86.76 | 89.93 | 0 | 0 | 0.0000% | 0.0000% | 3.17 | + +**Table G.2 – Simulation results summary GPON managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|--------|--------|------|-----|---------|---------|---------| +| | SDTV1_Down | bidi | 113079 | 86.76 | 89.87 | 0 | 0 | 0.0000% | 0.0000% | 3.11 | +| | | dwn | 113079 | 86.76 | 89.89 | 0 | 0 | 0.0000% | 0.0000% | 3.14 | +| | | up | 113079 | 86.76 | 89.45 | 0 | 0 | 0.0000% | 0.0000% | 2.69 | +| | VoIP1_Fwd | bidi | 20735 | 86.05 | 86.77 | 0 | 0 | 0.0000% | 0.0000% | 0.72 | +| | | dwn | 20735 | 86.05 | 86.77 | 0 | 0 | 0.0000% | 0.0000% | 0.72 | +| | | up | 20735 | 86.05 | 86.77 | 0 | 0 | 0.0000% | 0.0000% | 0.72 | +| | VoIP1_Rev | bidi | 20733 | 86.05 | 86.71 | 0 | 0 | 0.0000% | 0.0000% | 0.67 | +| | | dwn | 20733 | 86.05 | 86.07 | 0 | 0 | 0.0000% | 0.0000% | 0.02 | +| | | up | 20733 | 86.05 | 86.72 | 0 | 0 | 0.0000% | 0.0000% | 0.67 | +| Gw6t | HDTV1_Down | bidi | 451494 | 101.77 | 115.62 | 3 | 0 | 0.0007% | 0.0000% | 13.85 | +| | | dwn | 451492 | 101.77 | 115.62 | 5 | 0 | 0.0011% | 0.0000% | 13.85 | +| | | up | 451494 | 101.77 | 115.31 | 3 | 0 | 0.0007% | 0.0000% | 13.54 | +| | SDTV1_Down | bidi | 113077 | 101.77 | 115.27 | 0 | 0 | 0.0000% | 0.0000% | 13.50 | +| | | dwn | 113077 | 101.77 | 115.26 | 0 | 0 | 0.0000% | 0.0000% | 13.49 | +| | | up | 113076 | 101.77 | 114.96 | 1 | 0 | 0.0009% | 0.0000% | 13.19 | +| | SDTV2_Down | bidi | 114897 | 101.77 | 115.56 | 1 | 0 | 0.0009% | 0.0000% | 13.80 | +| | | dwn | 114897 | 101.77 | 115.56 | 1 | 0 | 0.0009% | 0.0000% | 13.79 | +| | | up | 114897 | 101.77 | 115.25 | 1 | 0 | 0.0009% | 0.0000% | 13.49 | +| | VoIP1_Fwd | bidi | 20735 | 101.05 | 101.78 | 0 | 0 | 0.0000% | 0.0000% | 0.73 | +| | | dwn | 20735 | 101.05 | 101.78 | 0 | 0 | 0.0000% | 0.0000% | 0.73 | +| | | up | 20735 | 101.05 | 101.78 | 0 | 0 | 0.0000% | 0.0000% | 0.73 | +| | VoIP1_Rev | bidi | 20733 | 101.05 | 101.72 | 0 | 0 | 0.0000% | 0.0000% | 0.67 | +| | | dwn | 20733 | 101.05 | 101.07 | 0 | 0 | 0.0000% | 0.0000% | 0.02 | +| | | up | 20733 | 101.05 | 101.73 | 0 | 0 | 0.0000% | 0.0000% | 0.68 | + +**Table G.2 – Simulation results summary GPON managed flows** + +| Case | File | Scen | n1 | min | max | drop | seq | drop % | seq % | max-min | +|-------------|-------------------|------|--------|--------|--------|------|-----|---------|---------|---------| +| Gw7t | HDTV1_Down | bidi | 451472 | 126.78 | 140.45 | 7 | 0 | 0.0016% | 0.0000% | 13.68 | +| | | dwn | 451475 | 126.78 | 140.73 | 4 | 0 | 0.0009% | 0.0000% | 13.95 | +| | | up | 451473 | 126.78 | 140.32 | 6 | 0 | 0.0013% | 0.0000% | 13.54 | +| | SDTV1_Down | bidi | 113072 | 126.78 | 140.10 | 0 | 0 | 0.0000% | 0.0000% | 13.32 | +| | | dwn | 113071 | 126.78 | 140.37 | 1 | 0 | 0.0009% | 0.0000% | 13.59 | +| | | up | 113071 | 126.78 | 139.97 | 1 | 0 | 0.0009% | 0.0000% | 13.19 | +| | SDTV2_Down | bidi | 114897 | 126.78 | 140.40 | 1 | 0 | 0.0009% | 0.0000% | 13.62 | +| | | dwn | 114897 | 126.78 | 140.67 | 1 | 0 | 0.0009% | 0.0000% | 13.89 | +| | | up | 114897 | 126.78 | 140.27 | 1 | 0 | 0.0009% | 0.0000% | 13.49 | +| | VoIP1_Fwd | bidi | 20734 | 126.05 | 126.79 | 0 | 0 | 0.0000% | 0.0000% | 0.74 | +| | | dwn | 20734 | 126.05 | 126.79 | 0 | 0 | 0.0000% | 0.0000% | 0.74 | +| | | up | 20734 | 126.05 | 126.79 | 0 | 0 | 0.0000% | 0.0000% | 0.74 | +| | VoIP1_Rev | bidi | 20732 | 126.05 | 126.74 | 0 | 0 | 0.0000% | 0.0000% | 0.69 | +| | | dwn | 20732 | 126.05 | 126.07 | 0 | 0 | 0.0000% | 0.0000% | 0.02 | +| | | up | 20732 | 126.05 | 126.74 | 0 | 0 | 0.0000% | 0.0000% | 0.69 | +| Gw8t | HDTV1_Down | bidi | 451455 | 152.08 | 158.84 | 5 | 0 | 0.0011% | 0.0000% | 6.76 | +| | | dwn | 451454 | 152.08 | 159.21 | 6 | 0 | 0.0013% | 0.0000% | 7.13 | +| | | up | 451456 | 152.08 | 158.58 | 4 | 0 | 0.0009% | 0.0000% | 6.50 | +| | VoIP1_Fwd | bidi | 20733 | 151.06 | 152.09 | 0 | 0 | 0.0000% | 0.0000% | 1.02 | +| | | dwn | 20733 | 151.06 | 152.09 | 0 | 0 | 0.0000% | 0.0000% | 1.03 | +| | | up | 20733 | 151.06 | 152.09 | 0 | 0 | 0.0000% | 0.0000% | 1.02 | +| | VoIP1_Rev | bidi | 20731 | 151.14 | 153.67 | 0 | 0 | 0.0000% | 0.0000% | 2.53 | +| | | dwn | 20731 | 151.14 | 151.27 | 0 | 0 | 0.0000% | 0.0000% | 0.13 | +| | | up | 20731 | 151.14 | 153.67 | 0 | 0 | 0.0000% | 0.0000% | 2.53 | + +**Table G.3 – Simulation results summary iPerf flow statistics** + +| Case | dir | Scen. | Mgmt. | iPerf bandwidth (Mbit/s) | | | | | iPerf one-way delay (ms) | | | | | RTT (ms) | | | +|------|-----|-------|------------|--------------------------|--------|---------|-----|------|--------------------------|--------|---------|-------|--------|----------|-------|--------| +| | | | | Mean | Median | Std Dev | Min | Max | Mean | Median | Std Dev | Min | Max | Avg | Min | Max | +| Dp1 | up | bidi | Partly Mgd | 2.9 | 2.9 | 0.1 | 0.0 | 3.0 | 229.8 | 232.8 | 29.1 | 11.2 | 285.7 | 240.4 | 22.4 | 528.8 | +| Dp1 | dwn | bidi | Partly Mgd | 5.4 | 5.5 | 2.1 | 0.0 | 12.4 | 26.1 | 23.2 | 42.9 | 11.0 | 1146.9 | 23.2 | 22.2 | 24.2 | +| Dp2 | up | bidi | Partly Mgd | 1.4 | 1.5 | 0.1 | 0.0 | 1.5 | 416.3 | 422.6 | 95.1 | 26.3 | 682.2 | 428.7 | 52.7 | 1094.3 | +| Dp2 | dwn | bidi | Partly Mgd | 2.2 | 1.9 | 1.6 | 0.0 | 9.1 | 46.2 | 31.0 | 130.8 | 26.0 | 2952.3 | 53.3 | 52.3 | 54.4 | +| Dp3 | up | bidi | Partly Mgd | 1.5 | 1.5 | 0.1 | 0.0 | 1.5 | 447.1 | 459.7 | 98.1 | 51.3 | 785.9 | 487.3 | 102.8 | 1129.2 | +| Dp3 | dwn | bidi | Partly Mgd | 2.0 | 1.6 | 1.5 | 0.0 | 8.0 | 77.8 | 61.6 | 100.7 | 51.1 | 2315.3 | 103.4 | 102.3 | 104.4 | +| Dp4 | up | bidi | Partly Mgd | 0.7 | 0.7 | 0.2 | 0.0 | 1.0 | 117.9 | 98.6 | 74.1 | 76.5 | 1498.5 | 197.6 | 153.1 | 763.3 | +| Dp4 | dwn | bidi | Partly Mgd | 0.7 | 0.7 | 0.3 | 0.0 | 2.7 | 98.7 | 89.3 | 40.1 | 78.3 | 1682.1 | 154.8 | 154.6 | 155.0 | +| Dp5 | up | bidi | Partly Mgd | 0.5 | 0.5 | 0.3 | 0.0 | 1.0 | 162.6 | 137.8 | 104.4 | 101.5 | 3561.3 | 327.5 | 203.2 | 1495.3 | +| Dp5 | dwn | bidi | Partly Mgd | 0.6 | 0.6 | 0.3 | 0.0 | 2.7 | 225.9 | 158.7 | 224.0 | 101.2 | 4679.8 | 203.6 | 202.6 | 204.7 | +| Dp6 | up | bidi | Partly Mgd | 0.5 | 0.5 | 0.2 | 0.0 | 1.0 | 249.0 | 219.9 | 100.5 | 201.5 | 1638.5 | 449.0 | 403.1 | 1058.4 | +| Dp6 | dwn | bidi | Partly Mgd | 0.5 | 0.4 | 0.3 | 0.0 | 2.1 | 226.1 | 211.2 | 65.1 | 201.1 | 1994.4 | 404.4 | 404.3 | 404.6 | +| Du1 | up | bidi | Unmgd | 2.9 | 2.9 | 0.1 | 0.0 | 3.0 | 231.0 | 233.2 | 29.0 | 11.2 | 280.1 | 240.5 | 22.4 | 533.0 | +| Du1 | dwn | bidi | Unmgd | 5.5 | 5.6 | 2.2 | 0.0 | 16.3 | 28.0 | 21.1 | 75.7 | 11.0 | 1485.2 | 23.2 | 22.2 | 24.2 | +| Du2 | up | bidi | Unmgd | 1.5 | 1.5 | 0.1 | 0.0 | 1.5 | 397.8 | 401.7 | 101.8 | 26.3 | 676.5 | 409.0 | 52.7 | 1055.2 | +| Du2 | dwn | bidi | Unmgd | 2.3 | 1.9 | 1.7 | 0.0 | 10.0 | 34.3 | 29.5 | 32.6 | 26.0 | 696.2 | 53.3 | 52.3 | 54.4 | +| Du3 | up | bidi | Unmgd | 1.5 | 1.5 | 0.1 | 0.0 | 1.5 | 420.3 | 419.0 | 100.8 | 51.3 | 815.7 | 455.9 | 102.8 | 1119.7 | +| Du3 | dwn | bidi | Unmgd | 2.0 | 1.7 | 1.5 | 0.0 | 9.7 | 66.6 | 56.1 | 70.3 | 51.1 | 1910.0 | 103.4 | 102.3 | 104.4 | +| Du4 | up | bidi | Unmgd | 0.7 | 0.7 | 0.2 | 0.0 | 1.0 | 105.7 | 94.4 | 36.3 | 76.5 | 441.8 | 178.4 | 153.1 | 447.4 | +| Du4 | dwn | bidi | Unmgd | 0.8 | 0.7 | 0.4 | 0.0 | 3.6 | 85.9 | 82.1 | 15.0 | 76.1 | 626.3 | 153.6 | 152.5 | 154.6 | +| Du5 | up | bidi | Unmgd | 0.6 | 0.6 | 0.2 | 0.0 | 1.0 | 130.2 | 119.3 | 34.8 | 101.5 | 516.4 | 230.0 | 203.2 | 580.1 | +| Du5 | dwn | bidi | Unmgd | 0.6 | 0.6 | 0.3 | 0.0 | 2.8 | 116.5 | 111.2 | 18.9 | 101.2 | 448.8 | 203.6 | 202.6 | 204.7 | +| Du6 | up | bidi | Unmgd | 0.5 | 0.5 | 0.2 | 0.0 | 1.0 | 232.2 | 219.4 | 47.2 | 201.5 | 858.8 | 430.7 | 403.1 | 1201.3 | + +**Table G.3 – Simulation results summary iPerf flow statistics** + +| Case | dir | Scen. | Mgmt. | iPerf bandwidth (Mbit/s) | | | | | iPerf one-way delay (ms) | | | | | RTT (ms) | | | +|------|-----|-------|------------|--------------------------|--------|---------|-----|------|--------------------------|--------|---------|-------|--------|----------|-------|--------| +| | | | | Mean | Median | Std Dev | Min | Max | Mean | Median | Std Dev | Min | Max | Avg | Min | Max | +| Du6 | dwn | bidi | Unmged | 0.6 | 0.5 | 0.4 | 0.0 | 3.4 | 215.8 | 206.4 | 42.5 | 201.1 | 1256.2 | 403.5 | 402.5 | 404.6 | +| Du7 | up | bidi | Unmged | 0.5 | 0.4 | 0.2 | 0.0 | 1.0 | 285.6 | 269.4 | 65.6 | 251.5 | 1429.8 | 530.5 | 503.2 | 1344.7 | +| Du7 | dwn | bidi | Unmged | 0.5 | 0.4 | 0.4 | 0.1 | 3.0 | 271.7 | 259.3 | 49.5 | 255.3 | 1108.8 | 504.6 | 504.7 | 504.7 | +| Dw1 | up | bidi | Well Mgd | 2.9 | 2.9 | 0.1 | 0.0 | 3.0 | 230.3 | 233.4 | 29.4 | 11.2 | 286.5 | 239.8 | 22.4 | 527.9 | +| Dw1 | dwn | bidi | Well Mgd | 5.4 | 5.6 | 2.2 | 0.0 | 13.2 | 24.8 | 20.8 | 54.4 | 11.0 | 1219.3 | 23.2 | 22.2 | 24.2 | +| Dw2 | up | bidi | Well Mgd | 2.9 | 2.9 | 0.1 | 0.0 | 3.0 | 242.5 | 246.3 | 32.5 | 26.2 | 302.5 | 266.7 | 52.4 | 537.0 | +| Dw2 | dwn | bidi | Well Mgd | 5.1 | 5.2 | 2.3 | 0.0 | 14.8 | 38.3 | 34.5 | 39.5 | 26.0 | 1040.6 | 53.2 | 52.2 | 54.2 | +| Dw3 | up | bidi | Well Mgd | 2.9 | 2.9 | 0.1 | 0.0 | 3.0 | 259.2 | 263.9 | 36.8 | 51.2 | 328.7 | 308.5 | 102.4 | 547.2 | +| Dw3 | dwn | bidi | Well Mgd | 4.2 | 4.5 | 2.2 | 0.0 | 11.3 | 64.6 | 62.9 | 25.0 | 51.0 | 746.8 | 103.2 | 102.2 | 104.2 | +| Dw4 | up | bidi | Well Mgd | 1.9 | 1.9 | 0.1 | 0.0 | 2.0 | 391.8 | 401.0 | 61.3 | 76.2 | 584.3 | 462.8 | 152.6 | 841.1 | +| Dw4 | dwn | bidi | Well Mgd | 2.5 | 2.1 | 1.9 | 0.0 | 8.4 | 106.1 | 93.1 | 121.9 | 76.0 | 2795.9 | 153.3 | 152.3 | 154.3 | +| Dw5 | up | bidi | Well Mgd | 1.0 | 1.0 | 0.1 | 0.0 | 1.0 | 724.9 | 740.4 | 139.2 | 86.5 | 1258.6 | 781.2 | 173.1 | 1728.2 | +| Dw5 | dwn | bidi | Well Mgd | 1.4 | 0.9 | 1.4 | 0.0 | 6.1 | 137.6 | 92.5 | 236.5 | -49.8 | 3944.4 | 174.5 | 174.5 | 174.5 | +| Dw6 | up | bidi | Well Mgd | 1.0 | 1.0 | 0.1 | 0.0 | 1.0 | 708.8 | 729.0 | 166.7 | 101.5 | 1488.6 | 783.3 | 203.1 | 1861.8 | +| Dw6 | dwn | bidi | Well Mgd | 1.3 | 1.0 | 1.1 | 0.0 | 4.9 | 166.1 | 114.7 | 229.6 | 101.0 | 4280.4 | 203.5 | 202.5 | 204.5 | +| Dw7 | up | bidi | Well Mgd | 1.0 | 1.0 | 0.1 | 0.0 | 1.0 | 717.5 | 729.1 | 175.9 | 126.5 | 1351.7 | 810.2 | 253.1 | 1798.6 | +| Dw7 | dwn | bidi | Well Mgd | 1.4 | 1.0 | 1.2 | 0.0 | 5.0 | 184.4 | 141.7 | 177.0 | 127.0 | 3464.5 | 254.0 | 253.4 | 254.5 | +| Dw8 | up | bidi | Well Mgd | 1.0 | 1.0 | 0.1 | 0.0 | 1.0 | 704.5 | 727.2 | 215.4 | 151.5 | 1631.3 | 850.7 | 303.1 | 2007.3 | +| Dw8 | dwn | bidi | Well Mgd | 1.2 | 1.3 | 0.7 | 0.0 | 2.2 | 266.9 | 203.7 | 266.6 | 152.0 | 5150.4 | 569.0 | 304.6 | 833.4 | +| Dp1 | dwn | dwn | Partly Mgd | 20.2 | 20.0 | 1.0 | 0.0 | 24.3 | 36.0 | 37.2 | 8.5 | 11.0 | 95.0 | 40.2 | 22.2 | 58.2 | +| Dp2 | dwn | dwn | Partly Mgd | 5.9 | 5.8 | 1.6 | 0.0 | 14.3 | 27.6 | 27.5 | 1.4 | 26.0 | 100.0 | 91.9 | 52.3 | 131.4 | +| Dp3 | dwn | dwn | Partly Mgd | 3.7 | 3.5 | 1.4 | 0.0 | 8.9 | 54.3 | 53.2 | 6.5 | 51.5 | 294.3 | 166.6 | 102.8 | 230.4 | +| Dp4 | dwn | dwn | Partly Mgd | 0.8 | 0.7 | 0.3 | 0.0 | 6.0 | 92.4 | 83.4 | 38.9 | 77.3 | 1794.5 | 250.7 | 153.7 | 347.6 | + +**Table G.3 – Simulation results summary iPerf flow statistics** + +| | | | | iPerf bandwidth (Mbit/s) | | | | | iPerf one-way delay (ms) | | | | | RTT (ms) | | | +|------|-----|-------|------------|--------------------------|--------|---------|-----|------|--------------------------|--------|---------|-------|--------|----------|-------|--------| +| Case | dir | Scen. | Mgmt. | Mean | Median | Std Dev | Min | Max | Mean | Median | Std Dev | Min | Max | Avg | Min | Max | +| Dp5 | dwn | dwn | Partly Mgd | 0.6 | 0.6 | 0.3 | 0.0 | 3.0 | 222.5 | 166.6 | 212.5 | 102.0 | 4681.6 | 326.6 | 203.5 | 449.7 | +| Dp6 | dwn | dwn | Partly Mgd | 0.5 | 0.4 | 0.3 | 0.0 | 2.7 | 222.3 | 207.5 | 63.1 | 203.2 | 1826.2 | 634.6 | 404.6 | 864.6 | +| Du1 | dwn | dwn | Unmgd | 24.2 | 24.2 | 1.0 | 0.0 | 24.3 | 30.6 | 31.6 | 8.1 | 11.0 | 43.7 | 40.2 | 22.2 | 58.2 | +| Du2 | dwn | dwn | Unmgd | 5.9 | 5.8 | 1.7 | 0.0 | 14.1 | 27.3 | 27.3 | 0.3 | 26.0 | 36.1 | 91.9 | 52.3 | 131.4 | +| Du3 | dwn | dwn | Unmgd | 4.0 | 3.6 | 1.7 | 0.0 | 12.1 | 53.0 | 52.7 | 0.9 | 51.1 | 73.2 | 166.4 | 102.3 | 230.4 | +| Du4 | dwn | dwn | Unmgd | 0.8 | 0.8 | 0.3 | 0.0 | 6.0 | 82.3 | 79.2 | 9.0 | 76.1 | 166.2 | 250.1 | 152.5 | 347.6 | +| Du5 | dwn | dwn | Unmgd | 0.7 | 0.6 | 0.3 | 0.0 | 3.0 | 111.7 | 107.3 | 14.8 | 101.2 | 276.7 | 326.1 | 202.6 | 449.7 | +| Du6 | dwn | dwn | Unmgd | 0.5 | 0.4 | 0.4 | 0.0 | 4.9 | 213.4 | 204.2 | 47.3 | 201.1 | 1372.2 | 633.5 | 402.5 | 864.6 | +| Du7 | dwn | dwn | Unmgd | 0.5 | 0.4 | 0.4 | 0.0 | 3.0 | 268.6 | 257.2 | 58.5 | 251.2 | 1506.6 | 795.1 | 502.6 | 1087.7 | +| Dw1 | dwn | dwn | Well Mgd | 25.2 | 25.3 | 1.2 | 0.0 | 33.3 | 28.2 | 29.0 | 7.8 | 11.0 | 41.9 | 40.2 | 22.2 | 58.2 | +| Dw2 | dwn | dwn | Well Mgd | 21.6 | 23.2 | 2.8 | 0.0 | 33.4 | 34.8 | 29.5 | 9.4 | 26.0 | 59.5 | 91.7 | 52.2 | 131.2 | +| Dw3 | dwn | dwn | Well Mgd | 13.8 | 14.5 | 4.2 | 0.0 | 23.3 | 59.2 | 52.9 | 12.5 | 51.0 | 231.4 | 166.2 | 102.2 | 230.2 | +| Dw4 | dwn | dwn | Well Mgd | 9.2 | 9.8 | 2.0 | 0.0 | 16.4 | 104.1 | 101.2 | 25.8 | 76.0 | 550.3 | 245.5 | 152.8 | 338.3 | +| Dw5 | dwn | dwn | Well Mgd | 3.6 | 3.4 | 1.3 | 0.0 | 6.3 | 92.2 | 88.5 | 14.6 | 86.7 | 238.5 | 278.3 | 173.1 | 383.6 | +| Dw6 | dwn | dwn | Well Mgd | 3.1 | 3.1 | 1.0 | 0.0 | 6.1 | 131.6 | 107.8 | 47.9 | 101.8 | 606.8 | 325.4 | 203.2 | 447.6 | +| Dw7 | dwn | dwn | Well Mgd | 2.7 | 2.6 | 1.0 | 0.0 | 5.8 | 151.6 | 130.9 | 46.2 | 126.9 | 665.7 | 403.0 | 253.4 | 552.6 | +| Dw8 | dwn | dwn | Well Mgd | 1.9 | 2.1 | 0.4 | 0.0 | 9.0 | 289.7 | 271.2 | 120.5 | 151.1 | 806.9 | 476.0 | 302.5 | 649.6 | +| Dp1 | up | up | Partly Mgd | 3.0 | 3.0 | 0.1 | 0.0 | 3.0 | 229.8 | 233.7 | 29.7 | 11.2 | 283.1 | 238.1 | 22.4 | 495.8 | +| Dp2 | up | up | Partly Mgd | 1.5 | 1.5 | 0.0 | 0.0 | 1.5 | 412.3 | 413.8 | 99.0 | 26.3 | 705.0 | 423.2 | 52.7 | 1038.6 | +| Dp3 | up | up | Partly Mgd | 1.5 | 1.5 | 0.0 | 0.0 | 1.5 | 420.6 | 433.4 | 118.1 | 51.3 | 802.3 | 455.8 | 102.8 | 1127.5 | +| Dp4 | up | up | Partly Mgd | 0.7 | 0.7 | 0.2 | 0.0 | 1.0 | 118.7 | 95.8 | 63.0 | 76.5 | 1370.3 | 195.1 | 153.1 | 774.0 | +| Dp5 | up | up | Partly Mgd | 0.6 | 0.5 | 0.2 | 0.0 | 1.0 | 145.3 | 125.1 | 80.7 | 101.5 | 3339.8 | 251.2 | 203.2 | 714.2 | +| Dp6 | up | up | Partly Mgd | 0.5 | 0.4 | 0.2 | 0.0 | 1.0 | 232.5 | 219.5 | 47.7 | 201.5 | 1395.7 | 432.5 | 403.1 | 1324.7 | + +**Table G.3 – Simulation results summary iPerf flow statistics** + +| Case | dir | Scen. | Mgmt. | iPerf bandwidth (Mbit/s) | | | | | iPerf one-way delay (ms) | | | | | RTT (ms) | | | +|------|-----|-------|------------|--------------------------|--------|---------|-----|------|--------------------------|--------|---------|-------|--------|----------|-------|--------| +| | | | | Mean | Median | Std Dev | Min | Max | Mean | Median | Std Dev | Min | Max | Avg | Min | Max | +| Du1 | up | up | Unmged | 3.0 | 3.0 | 0.1 | 0.0 | 3.0 | 230.6 | 235.2 | 29.5 | 11.2 | 285.1 | 239.0 | 22.4 | 496.4 | +| Du2 | up | up | Unmged | 1.5 | 1.5 | 0.0 | 0.0 | 1.5 | 398.5 | 410.6 | 110.2 | 26.3 | 663.4 | 410.7 | 52.7 | 1009.1 | +| Du3 | up | up | Unmged | 1.5 | 1.5 | 0.0 | 0.0 | 1.5 | 409.7 | 423.5 | 118.3 | 51.3 | 742.5 | 444.7 | 102.8 | 1081.2 | +| Du4 | up | up | Unmged | 0.7 | 0.7 | 0.2 | 0.0 | 1.0 | 106.7 | 94.3 | 50.2 | 76.5 | 854.3 | 179.8 | 153.1 | 1345.7 | +| Du5 | up | up | Unmged | 0.6 | 0.6 | 0.2 | 0.0 | 1.0 | 134.3 | 119.3 | 63.7 | 101.5 | 1028.9 | 233.1 | 203.2 | 1646.0 | +| Du6 | up | up | Unmged | 0.5 | 0.5 | 0.2 | 0.0 | 1.0 | 236.1 | 219.4 | 73.5 | 201.5 | 1394.1 | 430.3 | 403.1 | 1324.7 | +| Du7 | up | up | Unmged | 0.5 | 0.4 | 0.2 | 0.0 | 1.0 | 287.7 | 269.4 | 76.4 | 251.5 | 1597.6 | 530.4 | 503.2 | 1664.7 | +| Dw1 | up | up | Well Mgd | 3.0 | 3.0 | 0.1 | 0.0 | 3.0 | 230.2 | 233.5 | 29.8 | 11.2 | 283.1 | 238.5 | 22.4 | 495.5 | +| Dw2 | up | up | Well Mgd | 3.0 | 3.0 | 0.1 | 0.0 | 3.0 | 242.6 | 245.9 | 32.1 | 26.2 | 298.9 | 265.7 | 52.4 | 523.8 | +| Dw3 | up | up | Well Mgd | 3.0 | 3.0 | 0.1 | 0.0 | 3.0 | 257.8 | 265.1 | 39.0 | 51.2 | 384.2 | 303.7 | 102.4 | 507.8 | +| Dw4 | up | up | Well Mgd | 2.0 | 2.0 | 0.1 | 0.0 | 2.0 | 392.9 | 405.7 | 62.1 | 76.2 | 539.8 | 458.7 | 152.6 | 783.5 | +| Dw5 | up | up | Well Mgd | 1.0 | 1.0 | 0.0 | 0.0 | 1.0 | 697.1 | 726.5 | 171.2 | 86.5 | 1321.6 | 742.5 | 173.1 | 1704.8 | +| Dw6 | up | up | Well Mgd | 1.0 | 1.0 | 0.0 | 0.0 | 1.0 | 682.7 | 700.2 | 182.5 | 101.5 | 1331.3 | 739.9 | 203.1 | 1727.4 | +| Dw7 | up | up | Well Mgd | 1.0 | 1.0 | 0.1 | 0.0 | 1.0 | 699.2 | 721.8 | 187.6 | 126.5 | 1385.0 | 779.0 | 253.1 | 1457.6 | +| Dw8 | up | up | Well Mgd | 1.0 | 1.0 | 0.0 | 0.0 | 1.0 | 742.6 | 773.3 | 188.0 | 151.5 | 1404.1 | 842.2 | 303.1 | 1432.4 | +| Gp1 | up | bidi | Partly Mgd | 32.8 | 33.3 | 2.5 | 0.0 | 35.0 | 18.5 | 15.5 | 6.0 | 11.0 | 32.4 | 38.9 | 22.1 | 76.7 | +| Gp1 | dwn | bidi | Partly Mgd | 29.7 | 30.4 | 2.1 | 0.0 | 32.9 | 25.2 | 26.3 | 6.7 | 11.0 | 40.7 | 23.0 | 22.1 | 24.0 | +| Gp2 | up | bidi | Partly Mgd | 14.8 | 14.9 | 0.5 | 0.0 | 15.1 | 60.0 | 59.1 | 7.9 | 26.1 | 76.8 | 80.3 | 52.1 | 136.6 | +| Gp2 | dwn | bidi | Partly Mgd | 15.4 | 15.0 | 3.9 | 0.0 | 27.1 | 35.3 | 35.2 | 3.3 | 26.0 | 112.0 | 53.1 | 52.1 | 54.1 | +| Gp3 | up | bidi | Partly Mgd | 12.4 | 12.4 | 3.2 | 0.0 | 22.0 | 60.2 | 60.0 | 4.4 | 51.0 | 124.9 | 116.2 | 102.1 | 237.1 | +| Gp3 | dwn | bidi | Partly Mgd | 16.4 | 17.7 | 4.3 | 0.0 | 22.0 | 65.6 | 65.2 | 6.8 | 51.0 | 114.7 | 103.1 | 102.1 | 104.1 | +| Gp4 | up | bidi | Partly Mgd | 4.9 | 4.9 | 0.2 | 0.0 | 5.0 | 181.9 | 181.6 | 26.2 | 76.1 | 263.1 | 229.1 | 152.3 | 442.4 | +| Gp4 | dwn | bidi | Partly Mgd | 4.3 | 4.6 | 1.5 | 0.0 | 10.4 | 101.4 | 102.4 | 19.6 | 76.0 | 699.3 | 153.5 | 152.9 | 154.2 | + +**Table G.3 – Simulation results summary iPerf flow statistics** + +| Case | dir | Scen. | Mgmt. | iPerf bandwidth (Mbit/s) | | | | | iPerf one-way delay (ms) | | | | | RTT (ms) | | | +|------|-----|-------|------------|--------------------------|--------|---------|-----|------|--------------------------|--------|---------|-------|--------|----------|-------|--------| +| | | | | Mean | Median | Std Dev | Min | Max | Mean | Median | Std Dev | Min | Max | Avg | Min | Max | +| Gp5 | up | bidi | Partly Mgd | 1.9 | 1.9 | 0.2 | 0.0 | 2.0 | 353.9 | 364.4 | 90.9 | 101.2 | 1408.0 | 515.6 | 202.6 | 1672.1 | +| Gp5 | dwn | bidi | Partly Mgd | 2.0 | 2.2 | 0.9 | 0.0 | 4.9 | 214.0 | 193.6 | 123.0 | 101.1 | 2211.1 | 203.3 | 202.3 | 204.4 | +| Gp6 | up | bidi | Partly Mgd | 3.9 | 4.9 | 1.7 | 0.0 | 5.1 | 272.4 | 262.7 | 76.4 | 201.1 | 800.0 | 421.3 | 402.3 | 954.2 | +| Gp6 | dwn | bidi | Partly Mgd | 2.5 | 2.2 | 1.9 | 0.0 | 10.7 | 248.8 | 212.4 | 176.6 | 201.1 | 2331.4 | 403.6 | 403.0 | 404.2 | +| Gu1 | up | bidi | Unmgd | 33.8 | 34.7 | 2.4 | 0.0 | 35.0 | 24.0 | 25.3 | 5.4 | 11.0 | 32.6 | 37.8 | 22.1 | 64.1 | +| Gu1 | dwn | bidi | Unmgd | 33.5 | 34.6 | 2.6 | 0.0 | 35.0 | 18.3 | 16.2 | 5.2 | 11.0 | 33.0 | 23.0 | 22.0 | 24.0 | +| Gu2 | up | bidi | Unmgd | 14.8 | 14.9 | 0.6 | 0.0 | 15.1 | 61.0 | 60.1 | 7.6 | 26.1 | 78.1 | 80.7 | 52.1 | 133.8 | +| Gu2 | dwn | bidi | Unmgd | 15.3 | 14.9 | 4.0 | 0.0 | 30.2 | 33.8 | 33.6 | 2.7 | 26.0 | 78.2 | 53.1 | 52.1 | 54.1 | +| Gu3 | up | bidi | Unmgd | 15.6 | 16.3 | 3.9 | 0.0 | 23.0 | 63.0 | 63.2 | 5.0 | 51.0 | 116.9 | 108.7 | 102.1 | 233.6 | +| Gu3 | dwn | bidi | Unmgd | 16.0 | 16.6 | 3.6 | 0.0 | 23.3 | 64.3 | 64.4 | 5.9 | 51.0 | 184.5 | 103.1 | 102.1 | 104.1 | +| Gu4 | up | bidi | Unmgd | 4.9 | 5.0 | 0.3 | 0.0 | 5.1 | 186.0 | 186.2 | 26.4 | 76.1 | 236.9 | 225.9 | 152.3 | 406.3 | +| Gu4 | dwn | bidi | Unmgd | 4.5 | 4.9 | 1.8 | 0.0 | 10.5 | 96.0 | 95.5 | 36.4 | 76.0 | 1013.9 | 153.1 | 152.1 | 154.2 | +| Gu5 | up | bidi | Unmgd | 2.0 | 2.0 | 0.1 | 0.0 | 2.1 | 395.7 | 402.8 | 67.0 | 101.2 | 689.6 | 507.4 | 202.6 | 956.3 | +| Gu5 | dwn | bidi | Unmgd | 2.2 | 2.2 | 1.4 | 0.0 | 5.0 | 152.8 | 147.2 | 78.3 | 101.1 | 2393.0 | 203.3 | 202.3 | 204.4 | +| Gu6 | up | bidi | Unmgd | 3.9 | 5.0 | 1.8 | 0.0 | 5.1 | 271.2 | 257.8 | 81.7 | 201.1 | 815.3 | 417.3 | 402.3 | 909.3 | +| Gu6 | dwn | bidi | Unmgd | 2.4 | 1.9 | 2.0 | 0.0 | 9.7 | 256.9 | 208.8 | 218.3 | 201.1 | 2764.6 | 403.1 | 402.1 | 404.2 | +| Gu7 | up | bidi | Unmgd | 1.9 | 2.0 | 0.3 | 0.0 | 2.1 | 512.1 | 530.0 | 115.0 | 251.2 | 1265.4 | 571.1 | 502.6 | 1459.5 | +| Gu7 | dwn | bidi | Unmgd | 1.6 | 1.0 | 1.5 | 0.0 | 5.1 | 338.9 | 269.4 | 241.5 | 251.1 | 3528.8 | 503.3 | 502.3 | 504.4 | +| Gw1 | up | bidi | Well Mgd | 24.8 | 25.0 | 0.9 | 0.0 | 25.1 | 32.8 | 33.7 | 4.8 | 11.0 | 40.6 | 44.7 | 22.1 | 66.3 | +| Gw1 | dwn | bidi | Well Mgd | 17.7 | 17.3 | 3.2 | 0.0 | 36.7 | 19.8 | 19.9 | 1.1 | 11.0 | 24.0 | 23.0 | 22.0 | 24.0 | +| Gw2 | up | bidi | Well Mgd | 24.2 | 24.9 | 2.2 | 0.0 | 25.3 | 43.9 | 42.2 | 6.0 | 26.0 | 57.5 | 61.1 | 52.1 | 131.1 | +| Gw2 | dwn | bidi | Well Mgd | 16.2 | 15.7 | 4.8 | 0.0 | 36.1 | 33.1 | 33.1 | 2.4 | 26.0 | 90.8 | 53.0 | 52.0 | 54.0 | +| Gw3 | up | bidi | Well Mgd | 12.2 | 12.2 | 4.0 | 0.0 | 23.0 | 58.5 | 57.6 | 10.6 | 51.0 | 473.4 | 115.7 | 102.1 | 279.0 | + +**Table G.3 – Simulation results summary iPerf flow statistics** + +| Case | dir | Scen. | Mgmt. | iPerf bandwidth (Mbit/s) | | | | | iPerf one-way delay (ms) | | | | | RTT (ms) | | | +|------|-----|-------|------------|--------------------------|--------|---------|-----|------|--------------------------|--------|---------|-------|--------|----------|-------|-------| +| | | | | Mean | Median | Std Dev | Min | Max | Mean | Median | Std Dev | Min | Max | Avg | Min | Max | +| Gw3 | dwn | bidi | Well Mgd | 15.5 | 16.9 | 4.6 | 0.0 | 23.2 | 64.9 | 63.2 | 14.7 | 51.3 | 455.2 | 103.2 | 102.3 | 104.1 | +| Gw4 | up | bidi | Well Mgd | 11.6 | 12.9 | 4.7 | 0.0 | 17.4 | 84.4 | 82.9 | 7.5 | 76.0 | 255.2 | 158.3 | 152.1 | 336.5 | +| Gw4 | dwn | bidi | Well Mgd | 12.1 | 13.3 | 4.3 | 0.0 | 18.8 | 84.9 | 83.3 | 8.2 | 76.0 | 331.7 | 153.0 | 152.0 | 154.1 | +| Gw5 | up | bidi | Well Mgd | 9.0 | 9.4 | 2.7 | 0.0 | 14.8 | 97.2 | 96.5 | 20.1 | 86.0 | 886.5 | 181.8 | 172.1 | 376.7 | +| Gw5 | dwn | bidi | Well Mgd | 10.7 | 11.9 | 3.4 | 0.0 | 14.1 | 101.5 | 100.3 | 10.4 | 86.0 | 359.8 | 173.3 | 172.5 | 174.1 | +| Gw6 | up | bidi | Well Mgd | 7.0 | 7.3 | 2.7 | 0.0 | 13.5 | 111.2 | 108.3 | 31.8 | 101.0 | 1188.9 | 212.5 | 202.1 | 622.4 | +| Gw6 | dwn | bidi | Well Mgd | 9.2 | 10.4 | 3.0 | 0.0 | 12.4 | 115.6 | 112.8 | 13.2 | 101.3 | 459.9 | 203.2 | 202.4 | 204.1 | +| Gw7 | up | bidi | Well Mgd | 6.5 | 6.7 | 3.6 | 0.0 | 13.6 | 134.8 | 131.5 | 18.9 | 126.0 | 588.2 | 261.3 | 252.1 | 551.1 | +| Gw7 | dwn | bidi | Well Mgd | 7.6 | 8.1 | 2.9 | 0.0 | 13.2 | 138.6 | 135.1 | 14.0 | 126.4 | 588.3 | 253.4 | 252.7 | 254.1 | +| Gw8 | up | bidi | Well Mgd | 4.2 | 4.9 | 1.4 | 0.0 | 5.1 | 232.4 | 230.5 | 54.7 | 151.1 | 850.2 | 328.5 | 302.3 | 792.5 | +| Gw8 | dwn | bidi | Well Mgd | 3.2 | 3.4 | 1.9 | 0.0 | 7.2 | 194.0 | 180.7 | 106.5 | 151.4 | 2576.8 | 303.3 | 302.5 | 304.2 | +| Gp1 | dwn | dwn | Partly Mgd | 31.3 | 31.1 | 1.4 | 0.0 | 35.4 | 30.5 | 31.2 | 4.3 | 11.0 | 45.6 | 40.0 | 22.0 | 58.1 | +| Gp2 | dwn | dwn | Partly Mgd | 30.4 | 31.1 | 4.2 | 0.0 | 35.4 | 39.6 | 39.0 | 5.9 | 26.0 | 73.5 | 91.6 | 52.1 | 131.1 | +| Gp3 | dwn | dwn | Partly Mgd | 19.3 | 20.9 | 4.7 | 0.0 | 22.9 | 62.3 | 61.5 | 7.4 | 51.0 | 165.3 | 166.1 | 102.1 | 230.1 | +| Gp4 | dwn | dwn | Partly Mgd | 10.2 | 10.8 | 2.4 | 0.0 | 13.3 | 109.0 | 108.6 | 21.9 | 76.1 | 490.7 | 249.6 | 152.1 | 347.2 | +| Gp5 | dwn | dwn | Partly Mgd | 3.0 | 2.8 | 0.7 | 0.0 | 5.0 | 293.0 | 296.1 | 153.2 | 101.1 | 3366.0 | 325.8 | 202.3 | 449.4 | +| Gp6 | dwn | dwn | Partly Mgd | 4.5 | 4.6 | 2.9 | 0.0 | 11.1 | 215.1 | 210.4 | 20.0 | 201.1 | 935.0 | 633.1 | 402.1 | 864.2 | +| Gu1 | dwn | dwn | Unmgd | 35.3 | 35.4 | 1.2 | 0.0 | 35.4 | 29.2 | 30.2 | 3.9 | 11.0 | 33.7 | 40.0 | 22.0 | 58.1 | +| Gu2 | dwn | dwn | Unmgd | 34.2 | 35.4 | 4.8 | 0.0 | 35.4 | 38.5 | 37.5 | 5.1 | 26.0 | 48.2 | 91.6 | 52.1 | 131.1 | +| Gu3 | dwn | dwn | Unmgd | 20.2 | 22.0 | 5.0 | 0.0 | 23.3 | 57.7 | 55.6 | 4.8 | 51.0 | 71.0 | 166.1 | 102.1 | 230.1 | +| Gu4 | dwn | dwn | Unmgd | 12.8 | 14.7 | 3.9 | 0.0 | 15.1 | 86.4 | 84.2 | 8.2 | 76.0 | 107.3 | 249.6 | 152.1 | 347.2 | +| Gu5 | dwn | dwn | Unmgd | 5.0 | 5.0 | 0.4 | 0.0 | 5.1 | 205.2 | 209.9 | 35.6 | 101.1 | 282.7 | 325.8 | 202.3 | 449.4 | +| Gu6 | dwn | dwn | Unmgd | 4.9 | 4.3 | 3.6 | 0.0 | 12.2 | 211.1 | 207.5 | 18.5 | 201.1 | 935.1 | 633.1 | 402.1 | 864.2 | + +**Table G.3 – Simulation results summary iPerf flow statistics** + +| Case | dir | Scen. | Mgmt. | iPerf bandwidth (Mbit/s) | | | | | iPerf one-way delay (ms) | | | | | RTT (ms) | | | +|------|-----|-------|------------|--------------------------|--------|---------|-----|------|--------------------------|--------|---------|-------|--------|----------|-------|--------| +| | | | | Mean | Median | Std Dev | Min | Max | Mean | Median | Std Dev | Min | Max | Avg | Min | Max | +| Gu7 | dwn | dwn | Unmgd | 3.4 | 3.9 | 1.7 | 0.0 | 5.1 | 284.8 | 280.4 | 27.6 | 251.1 | 585.6 | 794.8 | 502.3 | 1087.4 | +| Gw1 | dwn | dwn | Well Mgd | 42.5 | 42.5 | 1.6 | 0.0 | 50.5 | 25.4 | 26.3 | 3.5 | 11.1 | 29.6 | 40.2 | 22.4 | 58.1 | +| Gw2 | dwn | dwn | Well Mgd | 38.5 | 40.5 | 6.5 | 0.0 | 41.2 | 32.9 | 32.3 | 3.7 | 26.0 | 39.8 | 91.5 | 52.0 | 131.1 | +| Gw3 | dwn | dwn | Well Mgd | 17.3 | 19.1 | 4.9 | 0.0 | 23.3 | 63.0 | 59.6 | 13.9 | 51.0 | 408.4 | 166.0 | 102.0 | 230.1 | +| Gw4 | dwn | dwn | Well Mgd | 12.8 | 14.3 | 4.6 | 0.0 | 19.1 | 86.1 | 87.0 | 7.0 | 76.0 | 257.3 | 245.0 | 152.0 | 338.1 | +| Gw5 | dwn | dwn | Well Mgd | 11.4 | 13.2 | 3.7 | 0.0 | 14.1 | 97.7 | 94.7 | 9.7 | 86.0 | 355.9 | 277.6 | 172.1 | 383.1 | +| Gw6 | dwn | dwn | Well Mgd | 9.6 | 11.1 | 3.2 | 0.0 | 13.1 | 113.5 | 110.8 | 12.7 | 101.3 | 410.0 | 324.7 | 202.3 | 447.1 | +| Gw7 | dwn | dwn | Well Mgd | 7.5 | 8.2 | 2.9 | 0.0 | 12.1 | 138.2 | 135.1 | 17.8 | 126.0 | 816.2 | 402.0 | 252.1 | 552.1 | +| Gw8 | dwn | dwn | Well Mgd | 5.8 | 7.1 | 2.4 | 0.0 | 8.6 | 186.2 | 184.5 | 24.9 | 151.5 | 508.4 | 475.9 | 302.6 | 649.2 | +| Gp1 | up | up | Partly Mgd | 35.3 | 35.3 | 1.2 | 0.0 | 35.4 | 29.3 | 30.3 | 3.9 | 11.0 | 33.7 | 32.7 | 22.1 | 105.1 | +| Gp2 | up | up | Partly Mgd | 15.1 | 15.1 | 0.5 | 0.0 | 15.2 | 64.5 | 63.3 | 7.5 | 26.1 | 79.0 | 76.1 | 52.1 | 206.1 | +| Gp3 | up | up | Partly Mgd | 20.0 | 22.0 | 5.0 | 0.0 | 23.3 | 59.6 | 60.6 | 6.1 | 51.0 | 78.8 | 105.8 | 102.1 | 365.1 | +| Gp4 | up | up | Partly Mgd | 5.0 | 5.0 | 0.2 | 0.0 | 5.1 | 191.1 | 190.3 | 25.8 | 76.1 | 241.9 | 221.3 | 152.3 | 540.2 | +| Gp5 | up | up | Partly Mgd | 2.0 | 2.0 | 0.1 | 0.0 | 2.0 | 420.7 | 423.5 | 60.2 | 101.2 | 1334.3 | 505.5 | 202.6 | 883.2 | +| Gp6 | up | up | Partly Mgd | 3.9 | 5.0 | 1.8 | 0.0 | 5.1 | 265.8 | 245.6 | 83.9 | 201.1 | 767.8 | 417.8 | 402.3 | 1324.2 | +| Gu1 | up | up | Unmgd | 35.3 | 35.4 | 1.2 | 0.0 | 35.4 | 29.3 | 30.3 | 3.9 | 11.0 | 33.8 | 32.6 | 22.1 | 105.1 | +| Gu2 | up | up | Unmgd | 15.1 | 15.2 | 0.5 | 0.0 | 15.2 | 64.5 | 63.2 | 7.5 | 26.1 | 78.8 | 76.0 | 52.1 | 206.1 | +| Gu3 | up | up | Unmgd | 20.3 | 22.0 | 5.1 | 0.0 | 23.4 | 60.5 | 62.9 | 5.9 | 51.0 | 80.8 | 106.0 | 102.1 | 365.1 | +| Gu4 | up | up | Unmgd | 5.0 | 5.0 | 0.2 | 0.0 | 5.1 | 191.0 | 189.4 | 24.8 | 76.1 | 237.1 | 221.8 | 152.3 | 540.2 | +| Gu5 | up | up | Unmgd | 2.0 | 2.0 | 0.1 | 0.0 | 2.1 | 416.7 | 418.5 | 56.6 | 101.2 | 708.0 | 500.1 | 202.6 | 701.4 | +| Gu6 | up | up | Unmgd | 3.9 | 5.0 | 1.8 | 0.0 | 5.1 | 268.7 | 253.3 | 84.0 | 201.1 | 767.3 | 418.1 | 402.3 | 1324.2 | +| Gu7 | up | up | Unmgd | 2.0 | 2.0 | 0.2 | 0.0 | 2.1 | 518.7 | 539.0 | 110.7 | 251.2 | 1306.5 | 575.9 | 502.6 | 1664.4 | +| Gw1 | up | up | Well Mgd | 25.2 | 25.3 | 1.0 | 0.0 | 25.3 | 37.2 | 38.4 | 4.8 | 11.0 | 42.6 | 43.3 | 22.1 | 105.1 | + +**Table G.3 – Simulation results summary iPerf flow statistics** + +| Case | dir | Scen. | Mgmt. | iPerf bandwidth (Mbit/s) | | | | | iPerf one-way delay (ms) | | | | | RTT (ms) | | | +|------|-----|-------|----------|--------------------------|--------|---------|-----|------|--------------------------|--------|---------|-------|-------|----------|-------|--------| +| | | | | Mean | Median | Std Dev | Min | Max | Mean | Median | Std Dev | Min | Max | Avg | Min | Max | +| Gw2 | up | up | Well Mgd | 24.4 | 25.3 | 3.7 | 0.0 | 25.3 | 45.9 | 45.3 | 6.7 | 26.0 | 57.9 | 55.3 | 52.1 | 206.1 | +| Gw3 | up | up | Well Mgd | 19.8 | 21.9 | 5.0 | 0.0 | 23.3 | 59.1 | 58.2 | 6.2 | 51.0 | 87.2 | 108.8 | 102.1 | 426.7 | +| Gw4 | up | up | Well Mgd | 13.1 | 14.1 | 4.1 | 0.0 | 17.4 | 83.4 | 80.4 | 8.1 | 76.0 | 253.5 | 156.8 | 152.1 | 523.1 | +| Gw5 | up | up | Well Mgd | 11.5 | 12.4 | 3.7 | 0.0 | 15.1 | 94.2 | 91.9 | 9.5 | 86.0 | 355.8 | 177.2 | 172.1 | 597.1 | +| Gw6 | up | up | Well Mgd | 9.5 | 11.0 | 3.3 | 0.0 | 13.1 | 108.4 | 104.5 | 11.1 | 101.0 | 420.9 | 207.0 | 202.1 | 690.1 | +| Gw7 | up | up | Well Mgd | 7.6 | 8.1 | 3.2 | 0.0 | 12.9 | 134.1 | 129.5 | 17.4 | 126.0 | 664.7 | 258.4 | 252.1 | 849.1 | +| Gw8 | up | up | Well Mgd | 4.4 | 5.0 | 1.3 | 0.0 | 5.1 | 239.1 | 243.1 | 55.5 | 151.1 | 617.5 | 322.8 | 302.3 | 1001.2 | + +# **Annex H** + +## **Electronic attachment** + +(This annex forms an integral part of this Recommendation.) + +The electronic attachment is downloadable from the ITU website and is a part of this Recommendation. This file may be converted into a physical DVD data disk using any of the available software tools or packages. The data disk contents are described on the disk itself and has the following subdirectories: + +ISO 9660 format file that is downloadable from the ITU website: + +- ./tc – Impairment combination standard test cases (clause 7.2); +- ./simulator.tar.gz – Ready-to-build distribution (Annexes B and H); +- ./pcap – Input packet capture files of interfering traffic (Annex C); +- ./D – DSL technology simulator output (Annex D); +- ./G – GPON technology simulator output (Annex D). + +# Appendix I + +## TCP considerations + +(This appendix does not form an integral part of this Recommendation.) + +This appendix is intended to explain some of the complexity added to the model due to the introduction of TCP. With TCP as a Layer 4 Protocol, wide variations in performance can result. This variation in performance is implementation dependent. + +With UDP transport of video using the MPEG transport mechanism (IPTV), encoder/decoder performance and network quality are the primary influences on the quality that users will experience. However, the particular implementation of UDP has little impact. This is because UDP is intended to be a simple protocol only for providing a sending and receiving port number, length value and header checksum. All other influences of the user's experience result from factors such as network bandwidth available, network loss and delay characteristics, as well as processor efficiency in the encoder and decoder. + +To the contrary, the performance of video transport over TCP can be very implementation dependent. Specifically, a particular Windows TCP stack may behave differently than a particular distribution of Linux. In addition, TCP implementations involve algorithms that make the source and destination dynamic, reacting to network conditions, round-trip-times (RTT) and available bandwidth. TCP flows will be negatively impacted by other traffic flows. If those flows are also TCP based, predicting the resulting conditions can be very complex. Even when the TCP session is created, the client and server modules will negotiate down to a common set of operating parameters. As a result, multiple clients may receive video flows differently even with the same set of network conditions and the same server. + +TCP stacks have evolved through several generations: Tahoe, Reno, New Reno, Compound and Cubic. In each generation, capabilities and options were added which could be tools for the developer of the TCP stack. We will review some of these options to help clarify the sources of some of these variations. + +**Selective acknowledgement (SACK):** If a packet is dropped, the receiving TCP entity would indicate it was still waiting for the dropped packet. That is, if packet n was dropped, and packet n+1 arrived, the receiver would indicate it was still expecting packet n+1 (The receiver always acknowledges a packet by announcing what packet it is now expecting). Even if packet n+2 and n+3 arrived, their acknowledgements would indicate that the receiver was expecting to receive n+1. The standard rule for TCP operation dictates that after three duplicate acknowledgements (four identical acknowledgements), the missing packet is declared to be lost and is retransmitted. In early implementations of TCP, our scenario would have seen the transmitting station resend packets n+1, n+2, and n+3. This duplication of transmitted packets wasted time and bandwidth. With a TCP implementation that supports SACK, only packet n+1 needs to be retransmitted. Many of the currently available TCP implementations support this. + +**Fast transmit/Fast recovery:** Normally, TCP uses a timer to determine when to retransmit a lost packet (for which three duplicate packets have not been received). In today's Internet/intranets with long, high speed links, many packets can be sent but not acknowledged before a retransmitted packet is correctly acknowledged. Fast retransmit allows for faster transmission of lost packets and faster recovery to the normal send rate. Normal policy for a sending station that determines that a packet has been lost is to drastically reduce the number of packets sent as a block and to lower the rate of increase of transmission. The rapidity with which the transmission level recovers varies considerably among the TCP variants. In older implementations the recovery is linear. Newer implementations use scaling that is likely to be more aggressive, reducing the time to reach the maximum estimated transmission rate. + +**Window scaling:** The window value, more properly window receive value, represents the number of bytes a receiver is announcing that they can properly receive. That is, it represents the available size of the receive buffer. In early implementations of TCP, the value was restricted to 64k bytes because the field in the TCP header that held the value was 16 bits. With modern high speed networks, this value has posed a significant limitation in filling links with packets. For example, a one gigabit/s link might be filled to 60-80 Mb/s before the window value was reached. Since the value of the window is negotiated at session start as part of the three-way handshake, either the sender or receiver can limit the value to 64k or below. To overcome this limitation, window scaling was introduced in newer implementations of TCP. In this procedure, the stations can negotiate the use of a window which is as large as 32 times 64k bytes. This significantly increases the ability of a station to saturate a link. + +# Appendix II + +## Hybrid box plots and violin plots + +(This appendix does not form an integral part of this Recommendation.) + +Many of the result plots in the electronic attachments are a hybrid of a box plot overlaying a violin plot [b-Violin]. These plots are an efficient way to visually display a lot of statistical information. + +A violin plot can be described as a rotated probability density function that has also been reflected across a vertical axis. In many cases the resulting shape looks like a violin. + +A box plot shows similar statistical information and is drawn as a box with whiskers and dots. The box is centred on the median value, and the upper and lower limits of the box represent the 25% and 75% quartiles of the data around the median. The whisker lines extend from the ends of the box and represent the 5%-95% ranges. The dots are drawn beyond the ends of the whiskers and represent the 1% outlier points of the data. + +Figure II.1 compares a probability density plot, violin plot and a box plot for 1000 data points generated from a normally distributed pseudo-random number generator. + + + +Figure II.1 displays three plots side-by-side, each representing a normal distribution (0, 1). The left plot is a 'Probability Density Plot' showing a smooth, symmetric bell curve centered at 0, with the y-axis ranging from 0.0 to 0.3. The middle plot is a 'Violin Plot', which is a rotated and reflected version of the density plot, showing the same bell shape centered at 0, with the y-axis ranging from -2 to 2. The right plot is a 'Box Plot', showing a horizontal box centered at 0, with whiskers extending to approximately -2 and 2, and a few small dots representing outliers. + +Figure II.1: Three plots comparing a Probability Density Plot, a Violin Plot, and a Box Plot for a normal (0, 1) distribution. + +**Figure II.1 – Density, violin, and box plots for a normal (0, 1) distribution** + +Some of the plots provided with the simulation results for this Recommendation are an overlay of a box plot with a violin plot. An example is given in Figure II.2. In addition, a 1-D density plot of the actual points is also added to the margin. + + + +Figure II.2 shows a combined violin-BFbox plot for a normal (0,1) distribution. The main plot is a violin plot with a box plot overlay, centered at 0. The y-axis ranges from -2 to 2. On the right side, there is a 1-D density plot (a rug plot) showing the distribution of the data points, with a vertical line at 0. + +Figure II.2: A combined violin-BFbox plot for a normal (0,1) distribution, showing a violin plot with a box plot overlay and a 1-D density plot in the margin. + +**Figure II.2 – Combined violin-BFbox plot for a normal (0,1)** + +# Appendix III + +## Simulation of high packet loss rates + +(This appendix does not form an integral part of this Recommendation.) + +Applications that use TCP are insulated from packet loss because the TCP protocol provides reliable delivery of data. TCP automatically detects when packets are lost and resends them. Therefore, at the application layer, the primary observable symptom of packet loss is increased latency. Applications such as video that depend upon continuous data transmission typically maintain a buffer in the receiver. The application reads from the buffer while the TCP layer writes received data into it. During steady state, the buffer remains at a constant level. When packet loss occurs, the application continues to read from the buffer while the transport layer (TCP) tries to recover from the loss and catch up with the application. If TCP recovery takes too long, for example because packet loss is severe, then the application buffer becomes empty and the video display freezes. It is safe to say that most Internet users have seen this phenomenon at one time or another. So when testing applications carried over TCP, packet loss is not as important as other network characteristics, such as latency. + +Of course, packet loss is still important to TCP algorithms because it is a normal and vital part of TCP's congestion and rate control mechanisms. Packets are typically lost when a network queue becomes full. This happens during times of high network utilization and congestion. It is during these periods of time that maximum delays also occur. Over time, link capacity can therefore be thought of in terms of both bandwidth and delay, and losses will occur during times of maximum delay on a link. For applications carried over RTP/UDP, a packet can be considered a lost packet if it exceeds a specified delay threshold. + +Therefore, high packet loss can be predicted using the empirical cumulative distribution function (CDF) of delay and the method described below. + +In this update of ITU-T G.1050, the simulation produces time series tables of bandwidth and delay for the unmanaged "best effort" link of the test cases defined by the Recommendation. An example plot of this for the case Dp4 in the downward direction is shown in Figure III.1. + +The cdf for each test case is provided in tabular form in six files called ./ {D|G} / out. {down|up|bidi} / cdf.csv. These files are part of the electronic attachment in Annex X. Each of these files has one test case per line, and each line has the cdf value for each percentile level. + +On the theory that excessively delayed packets are effectively lost packets, traffic periods that exceed a chosen delay bound can be considered dropped. As an example, consider the cdf values in Table III.1 and its plot in Figure III.2. For this test case, a 2% loss could be generated if packets exceeding 160.779 ms of delay were to be discarded. + + + +Figure III.1 – Downlink delay. A line graph titled 'iPerf: 1-way Delay:down: Dp4-t' showing average delay in milliseconds over time in seconds. The y-axis is logarithmic, ranging from 100 to 1000 ms. The x-axis ranges from 0 to 600 seconds. The graph shows a highly variable delay with many spikes. Summary statistics: Min=77.3, Max=1794.5, Mean=92.38, Median=83.43, StdDev=38.92. + +**Figure III.1 – Downlink delay** + +**Table III.1 – Example packet delay CDF data** + +| Pct. | Dly (ms) | Pct. | Dly (ms) | Pct. | Dly (ms) | Pct. | Dly (ms) | Pct. | Dly (ms) | +|------|----------|------|----------|------|----------|------|----------|------------|----------------| +| 0% | 77.300 | 20% | 81.244 | 40% | 82.660 | 60% | 84.434 | 80% | 98.222 | +| 1% | 79.030 | 21% | 81.320 | 41% | 82.738 | 61% | 84.622 | 81% | 99.305 | +| 2% | 79.310 | 22% | 81.434 | 42% | 82.810 | 62% | 84.810 | 82% | 100.179 | +| 3% | 79.520 | 23% | 81.530 | 43% | 82.870 | 63% | 84.970 | 83% | 100.953 | +| 4% | 79.690 | 24% | 81.590 | 44% | 82.940 | 64% | 85.240 | 84% | 102.135 | +| 5% | 79.831 | 25% | 81.675 | 45% | 82.990 | 65% | 85.579 | 85% | 103.482 | +| 6% | 79.961 | 26% | 81.740 | 46% | 83.070 | 66% | 86.133 | 86% | 104.699 | +| 7% | 80.060 | 27% | 81.800 | 47% | 83.139 | 67% | 86.627 | 87% | 105.954 | +| 8% | 80.150 | 28% | 81.866 | 48% | 83.230 | 68% | 87.080 | 88% | 107.338 | +| 9% | 80.252 | 29% | 81.930 | 49% | 83.330 | 69% | 87.821 | 89% | 109.744 | +| 10% | 80.340 | 30% | 82.000 | 50% | 83.430 | 70% | 88.636 | 90% | 111.494 | +| 11% | 80.430 | 31% | 82.080 | 51% | 83.480 | 71% | 89.670 | 91% | 114.031 | +| 12% | 80.530 | 32% | 82.130 | 52% | 83.560 | 72% | 90.630 | 92% | 116.294 | +| 13% | 80.610 | 33% | 82.210 | 53% | 83.631 | 73% | 91.669 | 93% | 120.589 | +| 14% | 80.710 | 34% | 82.260 | 54% | 83.700 | 74% | 92.559 | 94% | 124.939 | +| 15% | 80.833 | 35% | 82.330 | 55% | 83.780 | 75% | 94.160 | 95% | 128.780 | +| 16% | 80.900 | 36% | 82.380 | 56% | 83.900 | 76% | 95.035 | 96% | 135.242 | +| 17% | 80.993 | 37% | 82.450 | 57% | 84.000 | 77% | 95.905 | 97% | 146.009 | +| 18% | 81.094 | 38% | 82.530 | 58% | 84.100 | 78% | 96.672 | 98% | 160.779 | +| 19% | 81.184 | 39% | 82.600 | 59% | 84.270 | 79% | 97.440 | 99% | 188.326 | +| | | | | | | | | 100% | 1794.500 | + + + +iPerf: 1-way Delay:down: Dp4-t +(Min=77.3, Max=1794.5, Mean=92.38, Median=83.43, StdDev=38.92) + +Avg Delay (ms) + +dwn + +CDF plot of delay for iPerf 1-way down traffic on Dp4-t. The x-axis is 'Avg Delay (ms)' on a log scale from 100 to 1000. The y-axis is cumulative probability from 0.00 to 1.00. A red curve shows the distribution, starting at 0 at approximately 77.3 ms and reaching 1.0 at approximately 1794.5 ms. A legend entry 'dwn' is visible below the x-axis. + +**Figure III.2 – Delay CDF plot** + +# Bibliography + +- [b-ANSI/TIA-912C] TIA-912-C (2016), *Telecommunications – IP Telephony Equipment – Voice Gateway Transmission Requirements*. +- [b-ETSI TS 101 329-2] ETSI TS 101 329-2 (2002), *Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3, End-to-end Quality of Service in TIPHON systems; Part 2: Definition of speech Quality of Service (QoS) classes*. +- [b-IEEE 802.11A] IEEE 802.11A-1999, *IEEE standard for Telecommunications and Information Exchange Between Systems – LAN/MAN specific Requirements*. +- [b-IEEE 802.11B] IEEE 802.11B/COR 1-2001, *Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Higher Speed Physical Layer Extension in the 2.4 GHz Band*. +- [b-IEEE 802.11G] IEEE 802.11G-2003, *Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Further High Data Rate Extension in the 2.4 GHz Band*. +- [b-TIA-810-A] TIA-810-A (2004), *Telecommunications – Telephone Terminal Equipment – Transmission Requirements for Narrowband Voice over IP and Voice over PCM Digital Wireline Telephones*. +- [b-TIA-1001] TIA-1001 (2004), *Transport of TIA-825-A Signals over IP Networks*. +- [b-TIA TSB116A] TIA TSB116-A (2006), *Telecommunications – IP Telephony Equipment – Voice Quality Recommendations for IP Telephony*. +- [b-Cormen] Cormen, T., *et al.* (2001), *Introduction to Algorithms*, second edition, MIT Press and McGraw-Hill, ISBN 0-262-03293-7. +- [b-iPerf] Tirumala, Ajay, *et al.*, *Iperf: The TCP/UDP bandwidth measurement tool*.
(ignoring signs) | | Maximum individual
reading | | +|------------------------------------------------------|------------------------------------------------------------------------------------------|-----------------------------------------------------|-------------------------------|--------------------------------------------------------| +| | Type I | Types II, II bis ,
III and III bis | Type I | Types II, II
bis ,
III and III bis | +| Capacity unbalance in picofarads: | | | | | +| between pairs of the same quad | 33 | 17 | 125 | 60 | +| between pairs of adjacent quads in the same layer | 10 | 5 | 60 | 25 | +| between pairs in nonadjacent quads in the same layer | {mean value not specified
{because all possible
{combinations are not
{measured | | 20 | 10 | +| between pairs in quads in adjacent layers | 10 | 5 | 60 | 25 | +| between any pair and earth | 100 | 100 | 400 | 400 | + +*Note* - The limits shown for the mean values do not apply to cables which have four or less quads. + +TABLE 3/G.611 +**Mutual inductances** + +| | Mean of all readings
(ignoring signs) | | Maximum individual
reading | | +|---------------------------------------------------|------------------------------------------|-----------------------------------------------------|-------------------------------|-----------------------------------------------------| +| | Type I | Types II, II bis ,
III and III bis | Type I | Types II, II bis ,
III and III bis | +| Mutual inductances in nanohenrys: | | | | | +| between pairs of the same quad | 150 | 125 | 600 | 500 | +| between pairs of adjacent quads in the same layer | 100 | 40 | 400 | 150 | +| between pairs in nonadjacent quads | 50 | 20 | 350 | 150 | +| between pairs in quads in adjacent layers | 100 | 40 | 600 | 250 | + +*Note* - The limits shown for the mean values do not apply to cables which have four or less quads. + +For lengths greater than 230 metres, it is necessary to apply the following rules: + +The average values from pair to pair given in Tables 2/G.611 and 3/G.611 should be multiplied by the square root of the ratio between the length in question and 230 metres. + +All the maximum values, as well as the average values between a pair and earth, should be multiplied by the ratio between the length in question and 230 metres. + +Lengths shorter than 230 metres should satisfy the same conditions as the length of 230 metres. + +### 1.4 *Dielectric strength* + +When specially requested, cables will have a construction such that the insulation of any cable length should be capable of withstanding, without breakdown, a potential difference specified in each particular case but not exceeding 2000 volts r.m.s., applied for at least 2 seconds between all the conductors, connected together and the earthed sheath. The test can be made with a 50-Hz alternating current. The value of the test voltage should not exceed by more than 10% the peak value of a sinusoidal voltage having the same r.m.s. value. + +The test can also be carried out using direct current (see [1]). In such a case, the limit for the voltage will be 1.4 times the r.m.s. value of the voltage when using alternating current1). + +### 1.5 *Insulation resistance* + +In a length of cable, the insulation resistance measured between a conductor and all the other conductors connected together, and to the earthed sheath, should not be less than 10 000 M $\Omega$ -km, the potential difference used being at least 100 volts and not greater than 500 volts. The reading shall be made after electrification for one minute, the temperature being at least 15 °C. + +1) In reference [2], the CCITT does not recommend a formula for general application for tests on mixed dielectrics. However, for tests of telephone cables, the CCITT recommends the use of the factor 1.4 as representative of current commercial practice. + +## 2 Specification of a repeater section + +### 2.1 *Maximum attenuation in a repeater section* + +The maximum attenuation at the highest frequency transmitted to line of a normal repeater section shall be 41 dB for low-gain systems with 1, 2 or 3 groups and 36 dB for low-gain systems with 4 or 5 groups or 2 supergroups. + +### 2.2 *Crosstalk* + +The far-end crosstalk ratio between circuits in the same direction, measured on the repeater sections of a carrier system on unloaded symmetric pairs, terminated at their two ends by impedances equal to their characteristic impedance, should not be less than the values shown below (which allow for the existence of any crosstalk balancing networks). + +- 1) For the classical method of balancing, the repeater section far-end crosstalk ratio for low gain transistorized systems up to 120 channels on type II and III cables (or similar cables) or low-gain 120-channel systems on type II *bis* or III *bis* cables should not be less than 69.5 dB. +- 2) When a "balancing section" comprises several repeater sections, an equivalent result can be obtained from the formula $69.5 - 10 \log_{10} n$ (dB), where $n$ is the number of repeater sections in the balancing section. + +### 2.3 *Regularity of impedance* + +The impedance of any circuit in a repeater section forming part of a carrier system on unloaded symmetric pairs should not differ from the nominal value by more than the values shown below: + +- ± 5% (value measured at 60 kHz) for a repeater section forming part of a 12-channel system; +- ± 8% (value measured at 108 kHz) for a repeater section forming part of a 24-channel system; +- ± 8% (value measured at 120 kHz) for a repeater section forming part of a 36- or 48-channel system; +- ± 8% (value measured at 240 kHz) for a repeater section forming part of a 60-channel system; +- ± 8% (value measured at 552 kHz) for a repeater section forming part of a 120-channel system. + +### 2.4 *Dielectric strength* + +If it is desired to check the dielectric strength of a repeater section after laying, direct current will be applied to the cable at a voltage equal to the specified r.m.s. alternating current test voltage for tests on factory lengths (see § 1.4 above). + +### 2.5 *Insulation resistance* + +The insulation resistance measured at the end of the cable between any one conductor and all the other conductors bunched and connected to the earthed sheath (excluding internal repeater station wiring) should not be less than 10 000 M $\Omega$ -km measured at a potential difference of at least 100 volts and not more than 500 volts. The reading shall be made after electrification for one minute. + +## References + +- [1] *Dielectric strength tests*, Blue Book, Vol. III, Part 4, Annex 19, ITU, Geneva, 1965. +- [2] *Ibid.*, § 4. \ No newline at end of file diff --git a/marked/G/T-REC-G.654-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.654-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/G/T-REC-G.654-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d +size 7219 diff --git a/marked/G/T-REC-G.654-202408-I_PDF-E/raw.md b/marked/G/T-REC-G.654-202408-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..75d1a6a5b00b33c8d92e8e6d593a6d01c3dc772d --- /dev/null +++ b/marked/G/T-REC-G.654-202408-I_PDF-E/raw.md @@ -0,0 +1,723 @@ + + +# Recommendation **ITU-T G.654 (08/2024)** + +SERIES G: Transmission systems and media, digital systems and networks + +Transmission media and optical systems characteristics – +Optical fibre cables + +--- + +# **Characteristics of a cut-off shifted single-mode optical fibre and cable** + + + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features the letters 'ITU' in a bold, blue, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +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.654 + +# Characteristics of a cut-off shifted single-mode optical fibre and cable + +## Summary + +Recommendation ITU-T G.654 describes the geometrical, mechanical and transmission attributes of a single-mode optical fibre and cable which has the zero-dispersion wavelength around 1300 nm wavelength, and which is loss-minimized and cut-off wavelength shifted at around the 1550 nm wavelength region. This is the latest revision of this Recommendation that was first created in 1988. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.654 | 1988-11-25 | 15 | 11.1002/1000/886 | +| 2.0 | ITU-T G.654 | 1993-03-12 | 15 | 11.1002/1000/887 | +| 3.0 | ITU-T G.654 | 1997-04-08 | 15 | 11.1002/1000/4020 | +| 4.0 | ITU-T G.654 | 2000-10-06 | 15 | 11.1002/1000/5185 | +| 5.0 | ITU-T G.654 | 2002-06-29 | 15 | 11.1002/1000/6074 | +| 6.0 | ITU-T G.654 | 2004-06-13 | 15 | 11.1002/1000/7320 | +| 7.0 | ITU-T G.654 | 2006-12-14 | 15 | 11.1002/1000/8974 | +| 8.0 | ITU-T G.654 | 2010-07-29 | 15 | 11.1002/1000/10870 | +| 9.0 | ITU-T G.654 | 2012-10-29 | 15 | 11.1002/1000/11768 | +| 10.0 | ITU-T G.654 | 2016-11-13 | 15 | 11.1002/1000/13077 | +| 11.0 | ITU-T G.654 | 2020-03-15 | 15 | 11.1002/1000/14198 | +| 12.0 | ITU-T G.654 | 2024-08-29 | 15 | 11.1002/1000/16061 | + +## Keywords + +Cut-off shifted single-mode optical fibre and cable, large mode field diameter fibre, long haul transmission, optical fibre and cable. + +--- + +\* To access the Recommendation, type the URL
(Note 4) | Radius | TBD | mm | +| | Number of turns | TBD | | +| | Maximum at 1550 nm | TBD | dB | +| | Radius | 30 | mm | +| | Number of turns | 100 | | +| | Maximum at 1625 nm | 2.0 | dB | +| Proof stress (Note 2) | Minimum | 0.69 | GPa | +| Chromatic dispersion parameter | $D_{1550\max}$ | 23 | ps/(nm × km) | +| | $S_{1550\max}$ | 0.070 | ps/(nm 2 × km) | +| Uncabled fibre PMD coefficient | Maximum | (Note 3) | | +| Cable attributes | | | | +| Attribute | Detail | Value | Unit | +| Attenuation coefficient
(Note 1) | Maximum at 1550 nm | 0.20 | dB/km | +| PMD coefficient
(Note 3) | $M$ | 20 | cables | +| | $Q$ | 0.01 | % | +| | Maximum $PMD_Q$ | 0.20 | ps/√km | + +NOTE 1 – The attenuation coefficient values listed in this table should not be applied to short cables such as jumper cables. For example, [b-IEC 60794-2-11] specifies the attenuation coefficient of indoor cable as 1.0 dB/km or less. + +NOTE 2 – A higher proof stress may be considered depending on the applied system requirements. + +NOTE 3 – According to clause 7.2, a maximum $PMD_Q$ value on uncabled fibre is specified in order to support the primary requirement on cable $PMD_Q$ . + +NOTE 4 – Macrobending loss specification at 1550 nm may be useful in some systems. The specification values are to be determined including bending radius and number of turns. + +**Table 5 – ITU-T G.654.E attributes** + +| Fibre attributes | | | | +|-----------------------------------------|--------------------------|--------------|---------------------------| +| Attribute | Detail | Value | Unit | +| Mode field diameter | Wavelength | 1550 | nm | +| | Range of nominal values | 11.5-12.5 | μ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 (Note 1) | Maximum | 1530 | nm | +| Macrobending loss | Radius | 30 | mm | +| | Number of turns | 100 | | +| | Maximum at 1625 nm | 0.1 | dB | +| Proof stress | Minimum | 0.69 | GPa | +| Chromatic dispersion parameter (Note 2) | $D_{1550\max}$ | 23 | ps/(nm × km) | +| | $D_{1550\min}$ | 17 | ps/(nm × km) | +| | $S_{1550\max}$ | 0.070 | ps/(nm 2 × km) | +| | $S_{1550\min}$ | 0.050 | ps/(nm 2 × km) | +| Uncabled fibre PMD coefficient | Maximum | (Note 3) | | +| Cable attributes | | | | +| Attribute | Detail | Value | Unit | +| Attenuation coefficient (Note 4) | Maximum at 1550 nm | 0.23 | dB/km | +| | Maximum at 1530-1 612 nm | 0.25 | dB/km | +| | Maximum at 1 612-1625 nm | TBD (Note 5) | dB/km | +| PMD coefficient (Note 3) | $M$ | 20 | cables | +| | $Q$ | 0.01 | % | +| | Maximum $PMD_Q$ | 0.20 | ps/√km | + +NOTE 1 – When ITU-T G.654.E fibre is used at central frequencies for applications specified in [b-ITU-T G.698.2], corresponding to wavelengths in the range between 1527.8 and 1530 nm, then the cable cut-off wavelength should be less than 1527 nm. + +NOTE 2 – From 1530 nm to 1625 nm, chromatic dispersion coefficient $D(\lambda)$ at a given wavelength $\lambda$ can be specified by equation (6-1). + +NOTE 3 – According to clause 7.2, a maximum $PMD_Q$ value on uncabled fibre is specified in order to support the primary requirement on cable $PMD_Q$ . + +NOTE 4 – The attenuation coefficient values listed in this table should not be applied to short cables such as jumper cables. For example, [b-IEC 60794-2-11] specifies the attenuation coefficient of indoor cable as 1.0 dB/km or less. + +NOTE 5 – The attenuation increases at these longer wavelengths due to the macro/micro bending after the cabling process/deployment should be taken into account. Typically, an attenuation coefficient of 0.35 dB/km or less from 1612 nm to 1625 nm might be achieved. + +# Appendix I + +### Information about cabled fibre link attributes used for system design + +(This appendix does not form an integral part of this Recommendation.) + +In order to estimate transmission limitation due to fibre properties including chromatic dispersion, PMD, attenuation and nonlinearity, "worst-case" and "statistical" system designs can be considered as is given in clauses 9 and 10 of [b-ITU-T G-Sup.39], respectively. The worst-case design is a deterministic methodology utilizing minimum and maximum values, and is useful for a transmission system with a small number of components and spliced factory lengths of optical fibre cables. On the other hand, for a concatenated link that includes a large number of spliced factory lengths of optical fibre cable, the transmission parameters for the concatenated link must take into account not only the performance of the deterministic attributes of individual cable lengths, but also the statistics of concatenation. The requirements for factory lengths are given in clauses 6 and 7. + +The transmission characteristics of the factory length optical fibre cables will have a certain probability distribution, which can be taken into account if the most economic designs are to be obtained. This appendix should be read with the statistical nature of the various parameters in mind. + +Link attributes such as end-to-end attenuation, chromatic dispersion, PMD or nonlinearity are affected by factors other than optical fibre cables; by such things as splices, passive components and installation. These factors are not specified in this Recommendation. To estimate statistical link attribute values for attenuation and chromatic dispersion, typical values of optical fibre links are provided in clause I.4. The estimation methods for the link parameters needed for system design are based on measurements, modelling or other considerations. + +### I.1 Attenuation + +The mean attenuation $A$ of a link is given by: + +$$A = \alpha L + \alpha_s x + \alpha_{\text{con}} y \quad (\text{I-1})$$ + +where: + +$\alpha$ = mean attenuation coefficient of fibre cables in a link + +$\alpha_s$ = mean splice loss + +$x$ = number of splices in a link + +$\alpha_{\text{con}}$ = 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.). Equation I-1 does not include the loss of equipment connectors. The typical values found in clause I.5 are for the attenuation coefficient of an optical fibre link. 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 picoseconds per nanometre 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 6.10). + +When these fibres are used for transmission in the 1550 nm region, some forms of chromatic dispersion compensation are often employed. In this case, the average link chromatic dispersion is + +used for design purposes. The measured dispersion in the 1550 nm window can be characterized within the 1550 nm window by a linear relationship with wavelength. The relationship is described in terms of the typical chromatic dispersion coefficient and 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 are found in clause I.5. These values, together with link length, $L_{\text{Link}}$ , can be used to calculate the typical chromatic dispersion for use in optical link design. + +$$D_{\text{Link}}(\lambda) = L_{\text{Link}} [D_{1550} + S_{1550}(\lambda - 1550)] \quad (\text{ps/nm}) \quad (\text{I-2})$$ + +### I.3 Differential group delay + +The DGD is the difference in arrival times of the two polarization modes at a particular wavelength and time. PMD is fundamentally statistical and DGD fluctuates with random behaviour at any longitudinal positions of fibre cables, and therefore, statistical link design methodology is essential to determine PMD impact when considering a link made of a certain length of (or concatenated sections of) fibre cable. 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] and are summarized in Appendix IV of [ITU-T G.650.2]. The metrics of the limitations of the DGD distribution follow: + +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]. + +Reference link length, $L_{\text{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_c$ : 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, $\text{DGD}_{\text{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 $\text{DGD}_{\text{max}}$ . + +### I.4 Tables of common typical values + +The values in Tables I.1 and I.2 are representative of concatenated optical fibre links for submarine and terrestrial application, respectively, according to clauses I.1 and I.2. The implied fibre induced maximum DGD values in Table I.3 that are related to description in clause I.3 are intended for guidance with regard to the requirement for other optical elements that may be in the link. + +**Table I.1 – Representative values of a concatenated optical fibre link for submarine application** + +| Attribute | Detail | Value | +|-----------------------------------------|------------|---------------------------| +| Attenuation coefficient | Wavelength | Typical link value (Note) | +| | 1550 nm | 0.25 dB/km | +| | 1625 nm | TBD | +| Typical chromatic dispersion parameters | $D_{1550}$ | TBD | +| | $S_{1550}$ | TBD | + +NOTE – Typical link value corresponds to the link attenuation coefficient used in [b-ITU-T G.957] and [b-ITU-T G.696.1]. + +**Table I.2 – Representative values of a concatenated optical fibre link for terrestrial application** + +| Attribute | Detail | Value | +|-----------------------------------------|------------|---------------------------| +| Attenuation coefficient | Wavelength | Typical link value (Note) | +| | 1550 nm | TBD | +| | 1625 nm | TBD | +| Typical chromatic dispersion parameters | $D_{1550}$ | TBD | +| | $S_{1550}$ | TBD | + +NOTE – Typical link value corresponds to the link attenuation coefficient used in [b-ITU-T G.957] and [b-ITU-T G.696.1]. + +**Table I.3 – Differential group delay** + +| Maximum PMD 2
(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) | 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 – This value applies also for 10 Gbit Ethernet systems. + +NOTE – Cable section length is 10 km except for the 0.10 ps/km1/2 > 4 000 km link where, if set to 25 km, the probability level is $6.5 \times 10^{-8}$ . + +### I.5 Non-linear coefficient + +The effect of chromatic dispersion is interactive with the non-linear coefficient, $n_2/A_{\text{eff}}$ , where $A_{\text{eff}}$ denotes effective area, 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. Test methods for the non-linear coefficient remain under study. + +### I.6 An example of statistical methodology + +A mathematical approach for statistical link design can be taken when randomness can be assumed in designing a link (e.g., when a relatively large number of high-count cables are randomly concatenated to form a link), though its versatility is for further study. For example, when a concatenated link is composed of cabled fibre originated from a limited number of discrete fibres, a limited number of spooled fibres and cables, randomness is limited and the worst-case designing methodology is preferable to obtain reasonable system margins. + +General methodology for statistical system design is described in [b-ITU-T G-Sup.39], and the following provides one way to formulate a statistical upper limit for one of the fibre or cable parameters. + +The calculation starts with establishing a statistical distribution. Let $x_i$ and $L_i$ be a fibre parameter per unit length and a cable length, respectively, of a fibre in the $i$ th cable in a concatenated link of $N$ cables. In the case a global fibre parameter in the total link $x_N$ is in proportion the length, $x_N$ is: + +$$x_N = \frac{\sum_{i=1}^N L_i x_i}{\sum_{i=1}^N L_i} = \frac{1}{L_{\text{Link}}} \sum_{i=1}^N L_i x_i \quad (\text{I-3})$$ + +If it is assumed that all cable section lengths are less than some common value, $L_{\text{Cab}}$ , and simultaneously reducing the number of assumed cable sections to $M = L_{\text{Link}}/L_c$ , then, for a link comprised of equal-length cables, $L_i = L_c$ , equation (I-3) becomes + +$$x_N \leq x_M = \frac{L_c}{L_{\text{Link}}} \sum_{i=1}^M x_i = \frac{1}{M} \sum_{i=1}^M x_i \quad (\text{I-4})$$ + +The variation in the concatenated link parameter, $x_M$ , will be less than the variation in the individual cable sections, $x_i$ , because of the averaging of the concatenated fibres. + +Once a distribution of the fibre parameter has been established, the Monte Carlo method can be used to determine the probability density, $f_{\text{Link}}$ , of the concatenated link fibre parameter without making any assumption about its form. This method simulates the process of building links by sampling the measured fibre parameter population repeatedly. + +Fibre parameter is measured on a sufficiently large number of segments so as to characterize the underlying distribution. This data is then used to compute the fibre parameter for a single path in a concatenated link. + +Computation is made by randomly selecting $M$ values from the measured fibre parameters and adding them according to equation (I-4). The computed concatenated attenuation is placed in a table, or a histogram of values derived from other random samplings. The process is repeated until a sufficient number of concatenated attenuation values has been computed to produce a high-density histogram of the concatenated distribution of the fibre parameter. If the histogram is used directly without any additional characterization, such as Gaussian fitting, the number of samples should be at least $10^4$ . + +Because of the central limit theorem, the histogram of the statistical values of the fibre parameter in a concatenated cabled link will tend to converge to distributions that can be described with a minimum of two parameters. Hence, the histogram can be fitted to a parametric distribution that enables extrapolation to probability levels that are smaller than those implied by the sample size. The two parameters will invariably represent two aspects of the distributions: the central value and the variability about the central value. + +To obtain probability levels of $Q = 10^{-3}$ using a pure numeric approach requires Monte Carlo simulations of at least $10^4$ samples. Once this is complete, attenuation or chromatic dispersion can be interpolated from the associated cumulative probability density function. + +It should be noted that the applicability of the methodology used in this example is for further study. + +# Bibliography + +- [b-ITU-T G.663] Recommendation ITU-T G.663 (2016), *Application related aspects of optical amplifier devices and subsystems*. +- [b-ITU-T G.696.1] Recommendation ITU-T G.696.1 (2010), *Longitudinally compatible intra-domain DWDM applications*. +- [b-ITU-T G.698.2] Recommendation ITU-T G.698.2 (2018), *Amplified multichannel dense wavelength division multiplexing 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.973] Recommendation ITU-T G.973 (2016), *Characteristics of repeaterless optical fibre submarine cable systems*. +- [b-ITU-T G.973.1] Recommendation ITU-T G.973.1 (2009), *Longitudinally compatible DWDM applications for repeaterless optical fibre submarine cable systems*. +- [b-ITU-T G.973.2] Recommendation ITU-T G.973.2 (2011), *Multichannel DWDM applications with single channel optical interfaces for repeaterless optical fibre submarine cable systems*. +- [b-ITU-T G.977.1] Recommendation ITU-T G.977.1 (2020), *Transverse compatible dense wavelength division multiplexing applications for repeated optical fibre submarine cable systems*. +- [b-ITU-T G-Sup.39] Supplement ITU-T G-Sup.39 (2016), *Optical system design and engineering considerations*. +- [b-IEC 60794-2-11] IEC 60794-2-11:2019, *Optical fibre cables – Part 2-11: Indoor optical fibre cables – Detailed specification for simplex and duplex cables for use in premises cabling*. +- [b-IEC/TR 61282-3] IEC/TR 61282-3:2006, *Fibre optic communication system design guides – Part 3: Calculation of link polarization mode dispersion*. + + + +## 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.695-202505-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d5313aa1bc144955eccaf4ea8d30ff5b57852c5 --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d073b85b7247683b3177acdb5331016cfb3e402d250a400aaded8756357cfa07 +size 21500 diff --git a/marked/G/T-REC-G.695-202505-I_PDF-E/27788c2a26d9641e68232a4eff1299b9_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/27788c2a26d9641e68232a4eff1299b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4205d130db35577b4e69c9e574806c6421525704 --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/27788c2a26d9641e68232a4eff1299b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db3b7777c4e95e011b7d7d2ab81eaa73d6da71bb2a0ed63532230ef5fedb4848 +size 86389 diff --git a/marked/G/T-REC-G.695-202505-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf1d251a4a598f0548dba2d6573edbb629a26b2d --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ffb8c0fe03f23f7097d02ba4321c30638a1e7008f1b13307e03ab36bf52eed1 +size 56323 diff --git a/marked/G/T-REC-G.695-202505-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..477ba4e7f94f7c56f9e8e454baa740b967217d4d --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50d5f936257f72032daa38f9f8dffc017f502abdf9f1665bf347cb99127a75ce +size 49911 diff --git a/marked/G/T-REC-G.695-202505-I_PDF-E/664c1180d8c525b316fb0985ec1c5337_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/664c1180d8c525b316fb0985ec1c5337_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fdbc899e6f61ee8b6636041171839aefeb0e7d4 --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/664c1180d8c525b316fb0985ec1c5337_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:393636ee3b629955916645b1d269156045e9e3cf0ab16d77036a0cc09e430a80 +size 45174 diff --git a/marked/G/T-REC-G.695-202505-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/G/T-REC-G.695-202505-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f96b4a4a5297b1ed3f01509be5ef31467e1edd97 --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4860b94008a4c6495bbf7a9783e4bf2bc9660634c1be6aa4b533f4d8a7d1f5e +size 42930 diff --git a/marked/G/T-REC-G.695-202505-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bbcd666e7458acc407924984ced9344447a1949 --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3ac41d3a2a886a1cf02dbbb6416890f988d4dcbffc5e5f649ed329a0480ddc4 +size 28794 diff --git a/marked/G/T-REC-G.695-202505-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef020bfcd7fa0fc7fa3ad3b604bb0a1d9e5d9bce --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96767f636f98d53898a75c372cdbdb3bd279bd020ada328dc77ca01a76365d0a +size 56059 diff --git a/marked/G/T-REC-G.695-202505-I_PDF-E/e91d950121dbb814d5c91603c7cd146e_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/e91d950121dbb814d5c91603c7cd146e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df53b97c0ce6b2cef9c3971c61b6b3a5fbd21ad7 --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/e91d950121dbb814d5c91603c7cd146e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f32b095492b9d2da90c5624aa8f05a2d06da4b70248bf5e82af13e03c289635 +size 46715 diff --git a/marked/G/T-REC-G.695-202505-I_PDF-E/f164f105be425961ae10cd65296ddceb_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/f164f105be425961ae10cd65296ddceb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83ff91ca4051aa6fc5a141a0c6f2108a520034b8 --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/f164f105be425961ae10cd65296ddceb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e8b3aa8d9c1a89ebcf22e9ab374d8074116b86d0e4516757bbcfc8b5a3a5768 +size 32923 diff --git a/marked/G/T-REC-G.695-202505-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/G/T-REC-G.695-202505-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa561eb1767851a1d2ae05a3c744d04a8a334a3c --- /dev/null +++ b/marked/G/T-REC-G.695-202505-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f8daae81f82c1272c02b16215621fe162f8e4cde209c879186d376c2f8bd280 +size 64556 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..051ccff23225b07f288b1fedc4a9c4491f3501fc --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb447a713746cf179088774642e5a1eb7480698ecdf37f597a1d7a2428374df0 +size 146350 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/1b893df61c2b73b7a85e65fc1f58e203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6059d89c3c2aafc8fb1c85640724527a2a094ad --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/1b893df61c2b73b7a85e65fc1f58e203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03df6b9d75fb4975b3c95430f434312eb20647407f38679d1f24572e175f459e +size 62266 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38957ca5d135ff1d4e3a0889f3aa51a9390a8d52 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0eb867e488a73534a6a59111b7ef006fadd5a6269ae2d6caa891202d23ffaa4 +size 64161 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/2ba086df3506f81bae3a9b53725dcfea_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/2ba086df3506f81bae3a9b53725dcfea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82810d250e5f7588ef2ea2d8273762cf39980b0f --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/2ba086df3506f81bae3a9b53725dcfea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afad4b49c4d294bf76be5a42cd41f8b6716f3e04ea430612158c9fe4e2e93423 +size 52058 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56219a5fc2be39fa4c05291298387447ddfbde0e --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7e6c9c462d81ee9f3940ae9cd909b3d9b376d3a4125fb1e4b5630743438f098 +size 43401 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f30ea5630616cc1c8aa5abe8ffacc8e372f65490 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:045cd47ea5f748b17ad0300e2b4553b153330976339d9c535b6574d9ed1d0c9b +size 30230 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ae4499d017cdbf3a6171c8352586c5786876853 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bcd3958a1521233fbf066c30b3af4b2403f8cd6522f9fcbee1c5561b5a5e722 +size 149189 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1553dc45ec17b35ea7103973e220950d4425074 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11ccab001bce38eddc28bd0a5801e66e4ca9ca914ca57d86b6d67049bd21641d +size 114933 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d414e4e0640cfe78f99d418bed094a5738bab67 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6664f7b0174eb5b41d91fc6096f45db2f8b3b21163ae776436e67fdd8251bb53 +size 210242 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cff640017fc356ab78ad080653e9cc48271ca06 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c29a3b910ea530de709cd88ff5b810c6bcb17392ccf4b10d33e472a0550b9848 +size 86146 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c47c0438cde57c26bb7542cf3911f6e0c8c772f9 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45acec6c6e925a34c30119342a16a7ea05cb77a13d4515fa90fbc1501faf9b8e +size 79102 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b56320fa52882bf1f72ed34063b049c6953860c1 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ccaf6f7c4c4881ddf18e2b6504b110d3561ab485203bff043884c4e5105dfc1 +size 73402 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f806e9bf046ce7166a46a49cb8bf45917f51dfae --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba2c795ff35d497bd9c0ee9c8d605d5dfafa9baa3abb0e9b3f29ad9a225c5d81 +size 57753 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9744a9b5085ed35b347fab5b262f908379fb6259 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43d2f08fe73ab3792a300f2acc2302fd9c4dd71e7bc10e54787d59d5edfa77f4 +size 4369 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d66da181c6e6e42bf035d8ee98fad16279aa8e3 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19c7b6f788704ce324d2f2272f64f9d385f52f29dd61d09e686bcebe89f699d6 +size 39792 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcb2c54279d7feeb7312825650bb31c3f7d073b2 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ca7b4c523f23fb4d89851fbd01a1b72e2ea1d4433901cfb8182e843feecba6f +size 76362 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c995e96bfe0afd6dc10269c6763669b6507b558 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20b2cf3dacf79a2048b2a88bb4c45b2ca28ab2bc8a5796562c97b8ad556eb250 +size 70218 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..381049e3ab8f3b4367239b3bdaec1b3c46c72195 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d255ff605ff056eefecc56349401b13d5ad6738aa50872a96e1261d5ba47a811 +size 48125 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/G/T-REC-G.7042-200603-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ec9d5f44f41889800b733f412181b90b5e1ad7c --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91ee90c121c95c1feff554fab1fb9efa741cbc1bdb69a4b3010f495a95dee160 +size 62475 diff --git a/marked/G/T-REC-G.7042-200603-I_PDF-E/raw.md b/marked/G/T-REC-G.7042-200603-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a8680ef25890915969803838cf7c8c63fa0e64f0 --- /dev/null +++ b/marked/G/T-REC-G.7042-200603-I_PDF-E/raw.md @@ -0,0 +1,1169 @@ + + +**ITU-T** + +**G.7042/Y.1305** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/2006) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Data over Transport – Generic aspects – General + +SERIES Y: GLOBAL INFORMATION +INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS +AND NEXT-GENERATION NETWORKS + +Internet protocol aspects – Transport + +--- + +**Link capacity adjustment scheme (LCAS) for +virtual concatenated signals** + +ITU-T Recommendation G.7042/Y.1305 + +# 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 | +| 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 | +| 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.* + +# **Link capacity adjustment scheme (LCAS) for virtual concatenated signals** + +## **Summary** + +This Recommendation specifies a methodology for dynamically changing (i.e., increasing and decreasing) the capacity of a container that is transported in a generic transport network (e.g., over SDH or OTN network using Virtual Concatenation). In general, this change of capacity does not affect the traffic. In addition, the methodology also provides survivability capabilities, automatically decreasing the capacity if a member experiences a failure in the network, and increasing the capacity when the network fault is repaired. + +## **Source** + +ITU-T Recommendation G.7042/Y.1305 was approved on 29 March 2006 by ITU-T Study Group 15 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +Link capacity adjustment scheme, optical transport network, synchronous digital hierarchy, virtual concatenation. + +## 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 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 ..... | 1 | +| 4 Abbreviations..... | 2 | +| 5 Conventions ..... | 2 | +| 6 LCAS for virtual concatenation..... | 2 | +| 6.1 Methodology..... | 2 | +| 6.2 Control packet ..... | 3 | +| 6.3 VCG capacity increase (Addition of member(s))..... | 6 | +| 6.4 VCG capacity decrease: Member(s) temporary removed by the LCAS procedure (due to failure) ..... | 7 | +| 6.5 VCG capacity decrease: Removal (permanent) of member(s)..... | 8 | +| 6.6 LCAS to non-LCAS interworking..... | 8 | +| 6.7 Asymmetric connections ..... | 9 | +| 6.8 Symmetric connection ..... | 9 | +| Annex A – LCAS protocol..... | 10 | +| A.1 LCAS protocol..... | 10 | +| A.2 LCAS protocol partitioning..... | 12 | +| A.3 State diagram of member(i) in the Virtual Concatenated Group ..... | 14 | +| A.4 Procedures state diagrams ..... | 16 | +| A.5 State diagram for the VCG ..... | 20 | +| Appendix I – LCAS Time Sequence Diagrams ..... | 22 | +| I.1 Nomenclature ..... | 22 | +| I.2 Numbering system..... | 22 | +| I.3 Provisioning..... | 22 | +| I.4 Commands ..... | 22 | +| Appendix II – Non hit-less bandwidth modifications during Hold Off periods ..... | 29 | +| II.1 Introduction ..... | 29 | +| II.2 Removal of a group member at Source ..... | 29 | +| II.3 TSD conditions raised while performing ADD commands ..... | 29 | +| II.4 Enhanced HO procedure..... | 29 | + + + +# **Link capacity adjustment scheme (LCAS) for virtual concatenated signals** + +# **1 Scope** + +This Recommendation specifies a link capacity adjustment scheme that should be used to increase or decrease the capacity of a container that is transported in an SDH/OTN network using Virtual Concatenation. In addition, the scheme will automatically decrease the capacity if a member experiences a failure in the network and increase the capacity when the network fault is repaired. The scheme is applicable to every member of the Virtual Concatenation group. + +This Recommendation defines the required states at the source and at the sink side of the link as well as the control information exchanged between both the source and the sink side of the link to enable the flexible resizing of this Virtual Concatenated signal. The actual information fields used to convey the control information through the transport network are defined in their respective Recommendations, ITU-T Recs G.707/Y.1322 [1] and G.783 [3] for SDH and ITU-T Recs G.709/Y.1331 [2] and G.798 [4] for OTN. + +# **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.707/Y.1322 (2003), *Network node interface for the synchronous digital hierarchy (SDH)*. +- [2] ITU-T Recommendation G.709/Y.1331 (2003), *Interfaces for the Optical Transport Network (OTN)*. +- [3] ITU-T Recommendation G.783 (2006), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks*. +- [4] ITU-T Recommendation G.798 (2004), *Characteristics of optical transport network hierarchy equipment functional blocks*. +- [5] ITU-T Recommendation G.806 (2006), *Characteristics of transport equipment – Description methodology and generic functionality*. +- [6] ITU-T Recommendation Z.100 (2002), *Specification and Description Language (SDL)*. + +# **3 Terms and definitions** + +This Recommendation defines the following terms: + +**3.1 link:** A connection through a network from termination function to termination function. This can be related to the members of a virtual concatenation group as well as the virtual concatenation group itself. + +**3.2 member:** An individual server layer container that belongs to a virtual concatenated group. + +**3.3 virtual concatenation group (VCG):** A group of co-located member trail termination functions that are connected to the same virtual concatenation link. + +# **4 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|--------|---------------------------------------------------------------| +| CRC | Cyclic Redundancy Check | +| CTRL | Control field sent from source to sink | +| DNU | Do Not Use | +| EOS | End of Sequence | +| GID | Group Identification | +| HO | Hold Off | +| LCAS | Link Capacity Adjustment Scheme | +| MFI | MultiFrame Indicator | +| MI | Management Information | +| MST | Member Status | +| MSU | Member Signal Unavailable | +| MSU_L | Member Signal Unavailable, LCAS-enabled criteria | +| NORM | Normal Operating Mode | +| RS-Ack | Re-Sequence Acknowledge | +| Sk | Sink | +| So | Source | +| SQ | Sequence Indicator | +| TSD | Trail Signal Degrade | +| VCG | Virtual Concatenation Group | +| WTR | Wait-To-restore | +| $X_A$ | Actual number of members of a virtual concatenated group | +| $X_M$ | Maximum size of a virtual concatenated group | +| $X_P$ | Number of provisioned members in a virtual concatenated group | + +# **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 the most significant bit is transmitted first. The most significant bit (bit 1) is shown at the left in all the diagrams. + +# **6 LCAS for virtual concatenation** + +## **6.1 Methodology** + +LCAS in the virtual concatenation source and sink adaptation functions provides a control mechanism to hitlessly increase or decrease the capacity of a VCG link to meet the bandwidth needs of the application. Hitless bandwidth modification can only be achieved when the transmission of + +the active members belonging to the VCG – before and after the bandwidth modification – is error free (see Appendix II for details). It also provides the capability of temporarily removing member links that have experienced a failure. The LCAS assumes that in cases of capacity adjustment (i.e., creation, increase, decrease or deletion), the construction or destruction of the end-to-end path of each individual member is the responsibility of the Network and Element Management Systems. A VCG capacity increase or decrease can be initiated at either end. + +## 6.2 Control packet + +Synchronization of changes in the capacity of the transmitter (So) and the receiver (Sk) shall be achieved by a control packet. Each control packet describes the state of the link during the *next* control packet. Changes are sent in advance so that the receiver can switch to the new configuration as soon as it arrives. + +The control packet consists of fields dedicated to a specific function. The control packet contains information sent from So to Sk and information sent from Sk to So, see also Figure 1. + +Forward direction, So to Sk: + +- MultiFrame Indicator (MFI) field; +- Sequence Indicator (SQ) field; +- Control (CTRL) field; +- Group Identification (GID) bit. + +Return direction, Sk to So: + +- Member Status (MST) field; +- Re-Sequence Acknowledge (RS-Ack) bit. + +NOTE 1 – MST and RS-Ack are identical in the control packets of all members of the VCG. + +Both directions: + +- CRC field; +- Unused bits are reserved and shall be set to "0". + +NOTE 2 – To allow consistent timing relationships, it is assumed that the LCAS control packets are processed at the Sk after differential delay compensation. + + + +The diagram illustrates the structure of a control packet. It is divided into two main sections by vertical dashed lines. The left section, labeled 'information of member n, VCG\_a', contains the fields MST\_a(n), RS-Ack\_a, MFI\_a, SQ\_n, CTRL\_n, GID\_a, and CRC\_x. The right section, labeled 'information sent in control packet x of member\_n in VCG\_a', contains the fields MFI\_z, SQ\_p, CTRL\_p, GID\_z, CRC\_y, MST\_z(p), and RS-Ack\_z. At the far left, a triangle points to the left, labeled 'VCG\_a member\_n'. At the far right, a triangle points to the right, labeled 'VCG\_z member\_p'. A small label 'G.7042/Y.1305(06)\_F01' is at the bottom right. + +Diagram illustrating the allocation of information in a control packet. It shows two main sections: 'information of member n, VCG\_a' and 'information sent in control packet x of member\_n in VCG\_a'. The first section contains fields MST\_a(n), RS-Ack\_a, MFI\_a, SQ\_n, CTRL\_n, GID\_a, and CRC\_x. The second section contains fields MFI\_z, SQ\_p, CTRL\_p, GID\_z, CRC\_y, MST\_z(p), and RS-Ack\_z. The diagram also shows VCG\_a member\_n and VCG\_z member\_p at the ends, and a small label G.7042/Y.1305(06)\_F01 at the bottom right. + +Figure 1/G.7042/Y.1305 – Allocation of information in a control packet + +### 6.2.1 MultiFrame Indicator (MFI) field + +At the So side, the MFI is equal for all members of the VCG. At the Sk side, the MFI shall be used to realign the payload for all the members in the group. The MFI is used to determine the differential delay between members of the same VCG. See ITU-T Rec. G.806 for more details. + +### 6.2.2 Sequence Indicator (SQ) field + +Contains the sequence number assigned to a specific member. Each member of the same VCG is assigned a unique sequence number, starting at 0, similar to the Recommendations for Virtual Concatenation in ITU-T Recs G.707/Y.1322 [1] and G.709/Y.1331 [2]. + +The SQ is ignored at the Sk end for members sending IDLE in the control field. + +The SQ of a member of the VCG sending IDLE in the control field shall be set to the highest possible value. + +### 6.2.3 Control (CTRL) field + +The control field is used to transfer information from So to Sk. It shall be used to synchronize the Sk with the So and provide the status of the individual member of the group. + +**Table 1/G.7042/Y.1305 – LCAS CTRL words** + +| Value
msb...lsb | Command | Remarks | +|--------------------|---------|--------------------------------------------------------------------------| +| 0000 | FIXED | This is an indication that this end uses fixed bandwidth (non-LCAS mode) | +| 0001 | ADD | This member is about to be added to the group | +| 0010 | NORM | Normal transmission | +| 0011 | EOS | End of Sequence indication and Normal transmission | +| 0101 | IDLE | This member is not part of the group or about to be removed | +| 1111 | DNU | Do Not Use (the payload) the Sk side reported FAIL status | + +At initiation of a VCG source, all members shall send CTRL = IDLE until they are added to the VCG (and send CTRL = ADD). + +### 6.2.4 Group Identification (GID) bit + +Used for identification of the VCG. The GID bit of all members of the same VCG has the same value in the control packets with the same MFI. + +The GID provides the receiver with a means of verifying that all the arriving members originated from one transmitter. The contents are pseudo-random, but the receiver is not required to synchronize with the incoming stream. The pseudo-random pattern used is $2^{15} - 1$ . + +### 6.2.5 CRC field + +To simplify the validation of the changes in the virtual concatenation overhead, a CRC is used to protect each control packet. The CRC check is performed on every control packet after it has been received, and the contents rejected if the test fails. If the control packet passes the CRC test, then its contents are used immediately. To simplify MFI multi-framing, it is allowed to disregard the result of the control packet CRC check for the MFI element checked by the CRC so that the multi-framing process may use the MFI element equivalently with the non-LCAS virtual concatenation processing case. + +#### 6.2.5.1 CRC multiplication/division process + +The bits of the control packet can be regarded as the coefficients of a polynomial where the first bit of the control packet to be transmitted is the most significant bit. A particular CRC-n block is the remainder after multiplication of all bits in a control packet by $x^n$ and then division (modulo 2) by the application specific generator polynomial. The remainder is a polynomial of at most degree $(n - 1)$ . + +When representing the contents of the block as a polynomial, the first bit in the block, bit 1, should be taken as being the most significant bit. Consequently, $C_1$ is defined to be the most significant bit of the remainder and $C_n$ the least significant bit of the remainder. + +#### 6.2.5.2 CRC encoding procedure + +The control packet is considered to be static. This means that the CRC-n checksum can be calculated *a priori* over the control packet. + +The encoding procedure is as follows: + +- i) The CRC-n bits in the control packet are replaced by binary 0s. +- ii) The control packet is then acted upon by the multiplication/division process referred to in 6.2.5.1. +- iii) The remainder resulting from the multiplication/division process is inserted into the CRC-n location in the control packet. + +The CRC-n bits generated do not affect the result of the multiplication/division process because, as indicated in i) above, the CRC-n bit positions are initially set to 0 during the multiplication/division process. + +#### 6.2.5.3 CRC decoding procedure + +The decoding procedure is as follows: + +- i) A received control packet is acted upon by the division process referred to in 6.2.5.1. +- ii) If the remainder calculated in the decoder is zero, it is assumed that the checked control packet is error free. + +### 6.2.6 Member Status (MST) field + +Information about the status of all members of the same VCG is conveyed from Sk to So in the MST by member signals with control word ADD, NORM, EOS or DNU. + +It reports the member status from Sk to So with two states: OK or FAIL (1 status bit per member). OK = 0, FAIL = 1. Since each control packet contains only a limited number of bits for communicating the MST field, this information is spread across multiple control packets, an MST multiframe. + +The quantity of members in the VCG can be any number in the allocated range (e.g., 0-255 for High Order in SDH), and can be changed. For each member, the Sk uses the SQ number it receives from the So as the MST number for its response to the So. In this manner, the MST values received by the So will always correspond directly to the SQ values that it assigned. + +NOTE – In the non-LCAS mode, the receiver function is provisioned to expect a fixed number of members. + +To allow the receiver to determine the number of members in the VCG, the following should be noted. The highest non-failed active member will be indicating end of sequence (EOS) in the control field. The VCG may have other members with a higher SQ value in the do-not-use (DNU) state. + +At initiation of a VCG sink all members shall report MST = FAIL. A transition to MST = OK occurs when a control packet is received for that member with a control field of ADD (or NORM or EOS after it has been added, or DNU after recovery from a network failure). All unused MST and members that have a control field of IDLE shall be set to FAIL. + +### 6.2.7 Re-Sequence Acknowledge (RS-Ack) bit + +When a renumbering of the sequence numbers of the members sending in CTRL field NORM, DNU, EOS, or when a change of the number of these members is detected at the Sk, a notification to the So per VCG has to be performed by toggling (i.e., change from '0' to '1' or from '1' to '0') the RS-Ack bit. In particular, the causes that trigger the toggling of RS-Ack bit can be listed as follows (see also SDL diagrams for a detailed description of RS-Ack use): + +- SQ change for any VC of the VCG (SQ change detected by Sk for members in DNU/NORM/EOS); +- CTRL = "ADD" → CTRL = "EOS" and/or CTRL = "ADD" → CTRL = "NORM" (Addition of one or more members); +- CTRL = "NORM" (or "EOS") → CTRL = "IDLE" (Decrease bandwidth); +- CTRL = "DNU" → CTRL = "IDLE". + +NOTE 1 – Following an ADD command from management interface (i.e., when a transition CTRL = IDLE → CTRL = ADD occurs), no RS-Ack has to be transmitted. In fact, RS-Ack should be toggled only when a change in sequence of the members belonging to the VCG is detected at the Sink. During the first phase of the addition of new members (IDLE to ADD state transition), even if a SQ assignment may happen, it does not yet affect the VCG, therefore no RS-Ack is needed. + +The RS-Ack bit can only be toggled after the status of all members of the VCG has been evaluated and the sequence change has taken place. In case the RS-Ack is not sent to the So, the synchronization between Sk and So is achieved with the activation (during operations requiring a resequence or variation of the member's number in a VCG) of a RS-Ack time-out. The expiration of the time-out is equivalent to the detection of a toggled RS-Ack bit at So (refer to SDL protocol description, shown in Figures A.1 and A.7, for details). The toggling of the RS-Ack bit or the expiration of the RS-Ack time-out indicates that a new MST value can be considered. This means that MST values received in the control packet that contains the RS-Ack, and MST values received in subsequent control packets, correspond to the new sequence. The So can use this toggling as an indication that the change initiated by the So has been accepted and completed, and will start accepting new MST information. + +NOTE 2 – No new change in the VCG should be executed, i.e., no member should be added or removed from the VCG, until the RS-Ack is received or the RS-Ack timeout has expired for the currently active change request. + +## 6.3 VCG capacity increase (Addition of member(s)) + +When a member is added, it shall always be assigned a sequence number one larger than the currently highest sequence number that has EOS or DNU in the CTRL code. When multiple members are added, they must each use a unique sequence number so there will be a unique MST response for each additional member. + +Following an ADD command, the first member to respond with MST = OK shall be allocated the next highest sequence number and shall change its CTRL code to EOS coinciding with the currently highest member changing its CTRL code to NORM (or remains DNU). + +NOTE – When the CTRL = ADD is sent to initiate the addition of a new member, it shall be sent continuously until the MST = OK is received. + +In case more than one member (e.g., x) is being added, and MST = OK is being simultaneously received for those members, then the allocation of sequence indicators is arbitrary provided they are the next x sequence numbers after the currently highest sequence number (which has CTRL code EOS or DNU). The newly added members will have CTRL code NORM or EOS. The CTRL code for the currently highest member will change from EOS to NORM (or remains DNU) coinciding with the highest new member's CTRL code being changed to EOS. All other new member's CTRL codes will be set to NORM. + +### 6.3.1 Addition of member(s) payload + +The final step for adding a member is to send a NORM or EOS in the control field of the virtual concatenation overhead control packet for that member. The first container frame to contain payload data for the new member shall be the container frame immediately following the container frame that contained the last bit(s) (i.e., the CRC) of the control packet with NORM/EOS control field for that member. + +## 6.4 VCG capacity decrease: Member(s) temporary removed by the LCAS procedure (due to failure) + +### 6.4.1 Temporary removal of a member + +When a member sending a NORM or EOS experiences a failure in the Network, this is detected at the Sk (MSU\_L, TSD) and the Sk will send MST = FAIL for that particular member. The reporting of the MST = FAIL can be delayed by a Hold-Off time to limit the number of switch actions in case of nested protection mechanisms. Upon detection of the MST = FAIL, the So will either replace the NORM condition by a DNU condition, or replace the EOS condition with a DNU condition. The active member with the highest sequence number will send EOS in the CTRL field. + +#### 6.4.1.1 Temporary removal of a member's payload + +There are two reasons for a temporary removal of a member's payload: + +- In case of a received MSU\_L, the final step for temporary removal of a member is to remove that particular member from the VCG. At the Sk side, the removal shall start immediately after detection of the MSU\_L defect. At the So side, the last container frame that contains payload of the removed member shall be the container frame containing the last bit(s) of the control packet containing the first DNU control field. The following container frames will contain all ZEROes in the payload area. Upon reception at the Sk of the DNU control field, the payload of this particular member shall not be used to reconstruct the original VCG payload. +- In case of a received TSD, the final step for temporary removal of a member is to remove that particular member from the VCG. At the Sk side, the payload area of that particular member will continue to be used for the reconstruction of the original VCG payload. The bit errors in the payload area of the member have to be handled by the server to client adaptation function at the sink side of the VCG. At the So side, the last container frame that contains payload of the removed member shall be the container frame containing the last bit(s) of the control packet containing the first DNU code in the control field. The following container frames will contain all ZEROes in the payload area. Upon reception at the Sk of DNU in the control field, the payload area of that particular member is removed from the VCG. + +### 6.4.2 Reinstatement of temporarily removed member + +When the defect causing the temporary removal is cleared, this is detected at the Sk. The Sk will send MST = OK for that particular member. The reporting of the MST = OK can be delayed by a Wait-To-Restore time to avoid unwanted effects due to intermittent defects. Upon detection of the MST = OK, the So will either replace the DNU condition by a NORM condition, or replace the DNU condition with an EOS condition and the preceding member, that was sending CTRL code EOS, will send NORM in the CTRL field. + +#### 6.4.2.1 Reinstatement of temporarily removed members payload + +The final step after recovering from a temporary removal is to start using the payload area of that member again. The first container frame to contain payload data for the member shall be the container frame immediately following the container frame that contained the last bit(s) of the control packet containing the first CTRL code NORM or EOS in the control field for that member. + +## 6.5 VCG capacity decrease: Removal (permanent) of member(s) + +When members are deleted, the sequence numbers shall be renumbered. If the permanently removed member contained the highest sequence number of that group, the active member containing the next highest sequence number shall change its control field to EOS in its control packet coinciding with the permanently removed member's control packet with the IDLE control field. If the permanently removed member contained the highest sequence number of that group and sends DNU in the control field, the sequence numbering and control fields of the other members in the group will not change. If the permanent removal of a member occurs somewhere other than at the highest end of the sequence, then the other members with sequence numbers between the newly permanently removed member and the highest sequence number shall update their sequence indicators in their control packets coinciding with the control packet changing the status of the permanently removed member. + +Note that if permanent removal of members is initiated at the sink end first and the removed members were not the ones receiving signals with the highest SQ numbers, some of the remaining sink end members will receive SQ numbers higher than the new provisioned size at the sink end (until the members are removed at the source, too); this is not a fault condition. + +NOTE – If a permanent removal of an active member is initiated at the Sk, this will result in a hit to the reconstructed data in case the Remove Timer is set to the value '0' (zero) – see A.4.1 for details. The duration of this hit will be from the time the member is removed (starts sending MST = FAIL) until the DNU would have been received from the So. + +### 6.5.1 Deletion of member(s) payload + +When a member is deleted by sending an IDLE control field in the control packet on the virtual concatenation overhead for that member, the last container frame in which the deleted member contains payload data shall be the container frame containing the last bit(s) of the control packet containing the IDLE control field. + +## 6.6 LCAS to non-LCAS interworking + +Interworking between non-LCAS and LCAS Virtual Concatenation can be achieved as described in 6.6.1 and 6.6.2. Changes to the number of members in the VCG will be possible only by provisioning. + +### **6.6.1 LCAS transmitter and non-LCAS receiver** + +An LCAS transmitter can interwork with a non-LCAS receiver in non-LCAS mode without any special consideration. The LCAS transmitter will place the MFI and SQ as designated in ITU-T Recs G.707/Y.1322 [1] and G.709/Y.1331 [2]. The receiver will ignore all other bits, i.e., the LCAS overhead information. + +The member status returned from sink to source will always be MST = OK. + +### **6.6.2 Non-LCAS transmitter and LCAS receiver** + +An LCAS receiver expects a CTRL word that is not '0000' and a correct CRC. A non-LCAS transmitter will transmit '0000' in the LCAS CTRL field as well as the CRC field. Therefore, when an LCAS receiver is interworking with a non-LCAS transmitter and receives both CTRL word AND CRC equal to '0000', it shall: + +- Ignore all information (except MFI and SQ); +- Use MFI and SQ defect detection as defined for virtual concatenation. + +## **6.7 Asymmetric connections** + +The LCAS generally assumes directional independence of individual members of a virtually concatenated group. This implies connection asymmetry, i.e., the bandwidth of the forward transport is independent of the bandwidth of the return transport. Based on this consideration, the enclosed Specification and Description Language (SDL) diagrams in Annex A, and the time sequence diagrams, in Appendix I, only consider the asymmetric connectivity. + +## **6.8 Symmetric connection** + +This is for further study. + +Each constituent member in the virtually concatenated group has an accompanying member in the opposite direction (similar to bidirectional), the sink side status is only reported on its partner. + +If it is desired to keep the connection symmetric, this shall be provisionable from the Element Management System. + +# Annex A + +## LCAS protocol + +## A.1 LCAS protocol + +The operation of LCAS is unidirectional. This means that in order to bidirectionally add or remove members, the procedure has to be repeated in the opposite direction. Note that these actions are independent of each other and are therefore not required to be synchronized. When the transmission of members belonging to the VCG is error free, the scheme allows hitless addition and removal of bandwidth under control of a management system. Additionally, LCAS will autonomously remove failed members temporarily from the group. When the failure condition is remedied, LCAS will add the member back into the group. The removal of a member due to path layer failures will, in general, not be hitless for the service carried over the virtual concatenated group. The autonomous addition, after a failure is repaired, is hitless. + +In this model, there are three parameters to describe the virtual concatenated group of size -Xv: + +- 1) the parameter XM, which indicates the maximum size of the virtual concatenated group. This parameter is limited by specific definitions for each transport network technology (e.g., ITU-T Rec. G.707/Y.1322 for SDH, ITU-T Rec. G.709/Y.1331 for OTN) and may be further restricted to lower values in particular implementations; +- 2) the parameter XP, which indicates the number of provisioned members in the virtual concatenated group. Each completed ADD[i] command will increment XP by 1, each completed REMOVE[i] command will decrement XP by 1. Furthermore, the relationship $0 \leq X_P \leq X_M$ holds; +- 3) a parameter XA, which indicates the actual number of members of the virtual concatenated group as influenced by autonomous adding or deleting of members by the LCAS protocol in the case of individual member failures. The relationship $0 \leq X_A \leq X_P \leq X_M$ holds. + +Each parameter can then be further qualified in separate terms: when the source (transmit) or the sink (receive) end process need to be referenced specifically, "T" or "R" are added to the terms, respectively. For example, XPT is the provisioned number of members in the source (transmit) direction and XAR is the actual number of members in the sink (receive) direction. + +For each member (XMT times), there is a state machine at the source end that would be in one of the following five states: + +- 1) IDLE: This member is not provisioned to participate in the concatenated group. +- 2) NORM: This member is provisioned to participate in the concatenated group and has a good path to the sink end. +- 3) DNU: This member is provisioned to participate in the concatenated group and has a failed path to the sink end. +- 4) ADD: This member is in the process of being added to the concatenated group. +- 5) REMOVE: This member is in the process of being deleted from the concatenated group. + +For each member (XMR times), there is a state machine at the sink end that can be in one of the following three states: + +- 1) IDLE: This member is not provisioned to participate in the VCG. +- 2) OK: The incoming signal for this member experiences no failure condition (i.e., MSU\_L) or has received and acknowledged a request for addition of this member. When the incoming signal is degraded (i.e., TSD) the member remains in the OK state. + +- 3) FAIL: The incoming signal for this member experiences some failure condition or an incoming request for removal of a member has been received and acknowledged. + +These state machines run concurrently for all $X_{MT}$ source and $X_{MR}$ sink functions. + +To indicate in the SDL descriptions the possible events, the following notational conventions are used: + +- The following 5 control messages will be forwarded from the source end towards the sink end. A member will always forward one of these messages (so there are always $X_{MT}$ messages transmitted). The messages pertain to the member from which the message is sent. + - 1) $F_{IDLE}$ = Indication that this container is currently no member of the group and no ADD requests are pending; + - 2) $F_{ADD}$ = Request to add this member to the group; + - 3) $F_{DNU}$ = Indication that the payload of this member in the group shall not be used; + - 4) $F_{EOS}$ = Indication that this member has the highest sequence number among the active members in the group; + - 5) $F_{NORM}$ = Indication that this member is normal part of the group and does not have the highest sequence number. +- $C_{EOS}$ and $C_{NORM}$ are messages (source side only) from member(i) to member(i - 1), the previous in the sequence, to indicate that the control field sent by member(i - 1) shall be changed as requested. +- $R_{FAIL}$ and $R_{OK}$ are messages from sink to source about the status of the sink end of all members. The statuses of all sink ends are returned to the source end in the control packets of each member. The source end can, for example, read the information from member No. 1 and, if that is unavailable, the same information from member No. 2, etc. As long as no return bandwidth is available, the source end will use the last received valid status. +- $M_{ADD}$ and $M_{REMOVE}$ are messages from the management system to add or remove a member. The remove operation affects a specific member. Adding a new member is always at the end of the group with a new, highest, sequence number. +- $R_{RS-ACK}$ is a bit used to acknowledge the detection at the sink side of a renumbering of the sequence or a change in the number of members of the VCG. This acknowledgement is used to synchronize source and sink and to eliminate the influence of network delays. Due to the renumbering of the sequence at the time of an add or remove request, the received member status cannot be used for a time period that is determined by transmission delays and framing delays. +- $C_{RSQ}$ is a message (transmit source side only) from member(i) to member(i + 1), the next in the sequence, to indicate that the sequence number of member(i + 1) shall be decremented by 1. +- $S_{RSQ}$ is a message from the member state machines, at both source and sink side, to the VCG state machine to indicate that a change in the sequence numbering has taken place. + +The LCAS protocol is described in SDL diagrams to detail the state transitions. + +To avoid possible misalignment between $S_o$ and $S_k$ regarding the sequence numbers and the corresponding received far-end statuses, the number of provisioned members $X_p$ in the VCG is only changed under management command. + +The sequence number received just before an MSU\_L will be used for the reporting of the member status, but the payload will not be used to reconstruct the original signal. If the failed member is removed (by manager action), there will be a renumbering of the remaining sequence numbers. + +Replacement of a failed member (in the state DNU), because the failure in the network cannot be repaired, has to be performed via a REMOVE – ADD sequence. + +The SDL diagrams for the LCAS protocol description use the following conventions: + + + +| | | | +|--|----------------------------------------------------------------------|--------------------------------------------| +| | state | | +| | send | Forwarded CTRL word from So to Sk | +| | receive | | +| | send | Returned MST from Sk to So | +| | receive | | +| | send | Control sequence between members at the So | +| | receive | | +| | Management information input | | +| | server status input | | +| | re-sequence notification events from member part to VCG part | | +| | re-sequence request event from member(i) to member(i+1) | | +| | member state change notification event from member(i+1) to member(i) | | +| | timer events | | + +G.7042/Y.1305(06)\_FA.1 + +State diagram legend for G.7042/Y.1305. It defines symbols for states, send/receive operations, management information, and specific protocol events. state symbol send F symbol receive F symbol send R symbol receive R symbol send C symbol receive C symbol Management information input symbol server status input symbol re-sequence notification events symbol re-sequence request event symbol member state change notification event symbol timer events symbol + +**Figure A.1/G.7042/Y.1305 – State diagram legend** + +## A.2 LCAS protocol partitioning + +The LCAS functionality can be partitioned as follows: + +- Part of the protocol is performed at the Source side of the VCG; and +- Part of the protocol is performed at the Sink side of the VCG. + +Note that the flow of information from Source to Sink is per individual member of the VCG, i.e., SQ, CTRL, CRC and MFI. The flow of information from Sink to Source is per definition common for all members of the VCG. + +Using the flows a further partitioning can be made: + +- a) The part performing the functions at the Source side transmitting the information of each individual member to the Sink side, i.e., SQ, CTRL, CRC, MFI. SQ information is exchanged between the members of the VCG. SQ information is also sent to the receiving part to control the distribution of the member MST; +- b) The part performing the functions at the Sink side receiving the information of each individual member from the Source side and sending SQ and member status to the next part; +- c) The part performing the functions at the Sink side transmitting the information concerning all members of the VCG, i.e., the VCG member status as a whole and the acknowledge of a detected change in the VCG sequence numbering; + +- d) The part performing the functions at the Source side receiving the information concerning all members of the VCG, i.e., VCG MST and RS-Ack, and distributing the MST to each VCG member part. + +Figure A.2 illustrates these parts and shows the flow of information between the parts. + + + +Figure A.2/G.7042/Y.1305 – LCAS protocol partitioning diagram. The diagram shows Source and Sink sides, each with a VCG and member parts (i and i+1). Arrows indicate the flow of SQ, MST, RS-Ack, and SQ CTRL CRC MFI between these components. The label 'LCAS partitioning' is at the bottom left, and 'G.7042/Y.1305(06)\_FA.2' is at the bottom right. + +**Figure A.2/G.7042/Y.1305 – LCAS protocol partitioning** + +Figure A.3 shows the events exchanged between the separate parts of the LCAS protocol. + + + +Figure A.3/G.7042/Y.1305 – LCAS protocol flow of events diagram. This is a state transition diagram showing events like R\_ACK, R\_MST, R\_X, S\_RSQ, C\_RSQ, C\_X, R, and F. It is divided into Source and Sink sides, with VCG and member parts (i and i+1). Arrows show the flow of these events between the parts. The label 'LCAS flow of events' is at the bottom left, and 'G.7042/Y.1305(06)\_FA.3' is at the bottom right. + +**Figure A.3/G.7042/Y.1305 – LCAS protocol flow of events** + +## A.3 State diagram of member(i) in the Virtual Concatenated Group + + + +State diagram of member(i) with sequence number SQ(i) in a VCG with n provisioned members at the transmitting Source side + +``` + +stateDiagram-v2 + [*] --> Start + Start --> F_IDLE + F_IDLE --> IDLE + IDLE --> M_ADD + M_ADD --> SQ_inc1: SQ(i) := SQ(n)+1 + SQ_inc1 --> F_ADD + F_ADD --> ADD + + ADD --> R_OK + R_OK --> SQ_inc2: SQ(i) := SQ(n)+1 + SQ_inc2 --> n_inc: n := n+1 + n_inc --> F_EOS + F_EOS --> S_RSQ + S_RSQ --> C_NRM + C_NRM --> StartPayload: start sending payload + StartPayload --> NORM_EOS + + ADD --> M_REM + M_REM --> SQ_max: SQ(i) := (max) + SQ_max --> F_IDLE_back: F_IDLE + F_IDLE_back --> IDLE + + NORM_EOS --> C_RSQ_dec: C_RSQ / SQ(i) := SQ(i)-1 + C_RSQ_dec --> C_RSQ_out: C_RSQ + C_RSQ_out --> NORM_EOS + + NORM_EOS --> C_NRM_loop: C_NRM / F_NRM + C_NRM_loop --> NORM_EOS + + NORM_EOS --> C_EOS_trans: C_EOS / F_EOS + C_EOS_trans --> EOS_Decision + + EOS_Decision --> C_EOS_out: Y (is member sending EOS?) + C_EOS_out --> F_DNU + F_DNU --> StopPayload: stop sending payload + StopPayload --> DNU + + EOS_Decision --> NORM_EOS: N + + NORM_EOS --> R_FAIL + R_FAIL --> IDLE + + NORM_EOS --> M_REM_trans: M_REM + M_REM_trans --> DNU + + DNU --> C_RSQ_DNU: C_RSQ / SQ(i) := SQ(i)-1 + C_RSQ_DNU --> C_RSQ_DNU_out: C_RSQ + C_RSQ_DNU_out --> DNU + + DNU --> C_NRM_DNU: C_NRM / C_NRM + C_NRM_DNU --> SQ_Compare + + DNU --> C_EOS_DNU: C_EOS / C_EOS + C_EOS_DNU --> SQ_Compare + + SQ_Compare --> F_EOS_out: Y (SQ(i) > SQ of EOS member) + F_EOS_out --> C_NRM_out: C_NRM + C_NRM_out --> StartPayload_DNU: start sending payload + StartPayload_DNU --> NORM_EOS + + SQ_Compare --> F_NRM_out: N + F_NRM_out --> StartPayload_DNU + + DNU --> R_OK_DNU: R_OK + R_OK_DNU --> NORM_EOS + + DNU --> M_REM_DNU: M_REM + M_REM_DNU --> EOS_Decision_REM + + EOS_Decision_REM --> C_EOS_REM: Y (is member sending EOS?) + C_EOS_REM --> C_RSQ_REM: C_RSQ + C_RSQ_REM --> StopPayload_REM: stop sending payload + StopPayload_REM --> S_RSQ_REM: S_RSQ + S_RSQ_REM --> F_IDLE_REM: F_IDLE + F_IDLE_REM --> n_dec: n := n-1 + n_dec --> SQ_max_REM: SQ(i) := (max) + SQ_max_REM --> REMOVE + + EOS_Decision_REM --> C_RSQ_REM: N + + REMOVE --> R_FAIL_REM: R_FAIL + R_FAIL_REM --> IDLE + +``` + +Source side state diagram for a VCG member. The diagram shows transitions between IDLE, ADD, NORM/EOS, DNU, and REMOVE states based on control signals and sequence number logic. + +NOTE 1 – In case a single addition is issued, $F_{EOS}$ should be sent. Otherwise, in case of multiple and simultaneous additions, $F_{EOS}$ should be sent by the highest active member, $F_{NORM}$ by the other newly added members. + +NOTE 2 – The SQ of the removed member $i$ ( $0 \leq i < X_p$ ) shall be set to the highest possible value and the SQ of members with numbers $i + 1, \dots, (X_p - 1)$ will be renumbered to $i, \dots, (X_p - 2)$ . + +NOTE 3 – RS-Ack procedure is a process common to the whole VCG. + +G.7042/Y.1305(06)\_FA.4 + +**Figure A.4/G.7042/Y.1305 – Source side state diagram** + + + +``` + +graph TD + subgraph OK_State + OK((OK)) + TSD_c[TSD cleared] --> WTR[WTR] + TSD_r[TSD raised] --> HO[HO] + MSU_Lr[MSU_L raised] --> HO + F_IDLE[FIDLE] --> SQ_ch{SQ changed} + SQ_ch -- Y --> S_RSQ[SRSQ] + SQ_ch -- N --> R_FAIL[RFAIL] + M_REM[MREM] --> R_FAIL_REM[RFAIL] + R_FAIL_REM --> REMOVE[REMOVE procedure] + F_EOS[FEOS] --> START_READ[start/cont. reading payload] + F_NRM[FNRM] --> START_READ + START_READ --> SQ_ch2{SQ changed} + SQ_ch2 -- Y --> S_RSQ2[SRSQ] + SQ_ch2 -- N --> OK + F_DNU[FDNU] --> STOP_READ[stop reading payload] + STOP_READ --> OK + end + + subgraph FAIL_State + FAIL((FAIL)) + MSU_Lc[MSU_L cleared] --> SQ_corr{SQ correct} + F_ADD[FADD] --> SQ_corr + M_REM_F[MREM] --> FAIL + SQ_corr -- Y --> Fx{Fx?} + Fx -- ADD --> NRM_EOS_DNU[NRM/EOS/DNU] + NRM_EOS_DNU --> WTR_F[WTR] + WTR_F --> MSU_Lc2{MSU_L cleared} + MSU_Lc2 -- Y --> TSD_c2{TSD cleared} + TSD_c2 -- Y --> Fx2{Fx?} + Fx2 -- ADD/DNU --> NRM_EOS[NRM/EOS] + NRM_EOS --> START_READ_F[start reading payload] + START_READ_F --> R_OK[ROK] + end + + subgraph Start_Sequence + Start((Start)) --> R_FAIL_S[RFAIL] + R_FAIL_S --> STOP_READ_S[stop reading payload] + STOP_READ_S --> IDLE((IDLE)) + IDLE --> M_ADD[MADD] + end + +``` + +Sink side state diagram for a member in a VCG. The diagram is divided into two main sections: 'OK' and 'FAIL'. The 'OK' section shows transitions between states like 'TSD cleared', 'TSD raised', 'MSU\_L raised', 'F\_IDLE', 'M\_REM', 'F\_EOS', 'F\_NRM', and 'F\_DNU', with actions like 'WTR', 'HO', 'start/cont. reading payload', and 'stop reading payload'. The 'FAIL' section shows transitions between states like 'MSU\_L cleared', 'F\_ADD', 'M\_REM', 'SQ correct', 'Fx?', 'NRM/EOS/DNU', 'WTR', 'TSD cleared', 'ADD/DNU', 'start reading payload', and 'R\_ok'. A sub-diagram on the right shows a 'Start' state leading to 'R\_FAIL', 'stop reading payload', 'IDLE', and 'M\_ADD'. A title box in the top left reads 'State diagram of member(i) in a VCG with n provisioned members'. A label 'G.7042/Y.1305(06)\_FA.5' is in the bottom right. + +NOTE 1 – As per 6.2.2, no specific SQ is available at the sink after receiving a control word of "IDLE" for a member. MST = FAIL is generated here according to the general rule in Annex B/G.806 for members without validated SQ. + +NOTE 2 – This check verifies whether the SQ received for the present member is unique compared to those of the members in the OK state. If the received SQ is unique (i.e., not in use by any member among those in the OK state), the "y" branch is followed. Otherwise the "n" branch is followed. + +NOTE 3 – For a particular member(i), "hold off" and "wait to restore" procedures are never simultaneously active. + +**Figure A.5/G.7042/Y.1305 – Sink side state diagram** + +## A.4 Procedures state diagrams + +### A.4.1 REMOVE procedure + +The procedure describes the REMOVE timer activation and deactivation processes in order to allow hitless removal of a member from the VCG initiated at the Sink side. Figure A.6 shows the detailed SDL diagram for this procedure. + + + +``` +stateDiagram-v2 + [*] --> REMOVE_procedure : REMOVE procedure + REMOVE_procedure --> start_RMV_timer : start RMV timer + start_RMV_timer --> wait_to_REMOVE : wait to REMOVE + state "wait to REMOVE" as wait_to_REMOVE + wait_to_REMOVE --> F_DNU : F_DNU + wait_to_REMOVE --> F_IDLE : F_IDLE + wait_to_REMOVE --> MSU_L_raised : MSU_L raised + wait_to_REMOVE --> RMV_timer_expired : RMV timer expired + F_IDLE --> S_RSQ : S_RSQ + F_DNU --> stop_RMV_timer : stop RMV timer + F_IDLE --> stop_RMV_timer : stop RMV timer + MSU_L_raised --> stop_RMV_timer : stop RMV timer + RMV_timer_expired --> stop_RMV_timer : stop RMV timer + stop_RMV_timer --> [*] : stop RMV timer +``` + +G.7042/Y.1305(06)\_FA.6 + +State diagram for the REMOVE procedure. It starts with a 'REMOVE procedure' state, followed by a 'start RMV timer' transition. The next state is 'wait to REMOVE'. From this state, four transitions are possible: 'F\_DNU', 'F\_IDLE', 'MSU\_L raised', and 'RMV timer expired'. The 'F\_IDLE' transition leads to an 'S\_RSQ' state. All four transitions lead to a 'stop RMV timer' transition, which then leads to a final state (circle with an X). + +NOTE 1 – The 'wait to REMOVE' state is only a transitory state needed to get confirmation from the Source that it has recognized that a member will be removed by the Sink. Only after this confirmation is received, will the member payload be discarded. In this way, any other potential changes in the VCG, that the Source may initiate, is precluded. + +NOTE 2 – In case the value of the Remove-timer is set to 0 (zero), the REMOVE procedure is disabled, and the LCAS process behaves as defined in the 2004 version of ITU-T Rec. G.7042/Y.1305. + +**Figure A.6/G.7042/Y.1305 – REMOVE procedure** + +### A.4.2 RS-Ack procedure + +This procedure describes the RS-Ack detection process, used for validating the received MST. RS-Ack procedure is a process common to the whole VCG that is activated by a single member. Figure A.7 shows the detailed SDL diagram for this procedure. + + + +``` +graph TD; Entry([RS-Ack procedure]) --> Start[Start RS-Ack Time Out]; Start --> Wait([Wait for RS-Ack]); Wait --> MI_REM[MI_REM]; MI_REM --> Delay[Delay MI]; Delay --> Start; Wait --> Received[RS-Ack received]; Received --> Stop[Stop RS-Ack time out]; Wait --> Expired[RS-Ack Time Out expired]; Stop --> Exit((X)); Expired --> Exit; Delay --> Exit; G7042[Y.1305(06)_FA7] +``` + +SDL diagram for the RS-Ack procedure. The process starts with an oval 'RS-Ack procedure' entry point, leading to a parallelogram 'Start RS-Ack Time Out'. This leads to an oval 'Wait for RS-Ack' state. From this state, three paths emerge: 1) 'MI\_REM' (parallelogram) leading to 'Delay MI' (parallelogram), which loops back to the 'Start RS-Ack Time Out' path; 2) 'RS-Ack received' (parallelogram) leading to 'Stop RS-Ack time out' (parallelogram); 3) 'RS-Ack Time Out expired' (parallelogram). All three paths converge to a circle with an 'X' (exit point). The label 'G.7042/Y.1305(06)\_FA7' is next to the exit point. + +NOTE – The 'wait for RS-Ack' state is only a transitory state needed as a confirmation that the Source needs before accepting the new MST value assignment. In this way, any other potential changes in the VCG, that the Source may initiate, is precluded. + +**Figure A.7/G.7042/Y.1305 – RS-Ack procedure** + +### A.4.3 WTR procedure + +This procedure describes the wait-to-restore (WTR) timer activation and deactivation processes in order to avoid unwanted effects due to fleeting alarms, as described in ITU-T Rec. G.808.1. Figure A.8 shows the detailed SDL diagram for this procedure. + + + +``` +graph TD; Start([WTR procedure]) --> StartTimer{{Start WTR timer}}; StartTimer --> Wait([Wait for time-out]); Wait --> WTR_expired{WTR timer expired}; Wait --> MI_REM{MI_REM}; Wait --> MSU_L_raised{MSU_L raised}; Wait --> TSD_raised{_TSD raised}; MI_REM --> DelayMI[/Delay MI/]; WTR_expired --> StopTimer{{Stop WTR timer}}; DelayMI --> StopTimer; MSU_L_raised --> StopTimer; TSD_raised --> StopTimer; StopTimer --> End((X)); +``` + +G.7042/Y.1305(06)\_FA.8 + +SDL diagram for the WTR procedure. The process starts with a start symbol 'WTR procedure', followed by 'Start WTR timer'. It then enters a 'Wait for time-out' state. From this state, four parallel paths emerge: 'WTR timer expired', 'MI\_REM', 'MSU\_L raised', and '\_TSD raised'. The 'MI\_REM' path includes a 'Delay MI' block. All four paths converge to a 'Stop WTR timer' block, which leads to an end symbol (circle with an X). The diagram is labeled G.7042/Y.1305(06)\_FA.8. + +Figure A.8/G.7042/Y.1305 – WTR procedure + +### A.4.4 HO procedure + +This procedure describes the Hold Off (HO) timer activation and deactivation processes in order to limit the number of switch actions in case of nested protections, as described in ITU-T Rec. G.808.1. Figure A.9 shows the detailed SDL diagram for this procedure. + + + +``` +graph TD; Start([HO procedure]) --> Input1{{Start HO timer}}; Input1 --> Wait([Wait for time-out]); Wait --> Branch(( )); Branch --> Path1[/HO timer expired/]; Branch --> Path2[MI_REM]; Path2 --> Delay[/Delay MI/]; Delay --> Input2{{Stop HO timer}}; Path1 --> End((X)); Input2 --> End; G.7042/Y.1305(06)_FA.9 +``` + +SDL diagram for the HO procedure. The process starts with a start symbol 'HO procedure', followed by an input symbol 'Start HO timer'. It then enters a wait state 'Wait for time-out'. From this state, it branches into two parallel paths: one labeled 'HO timer expired' and the other 'MI\_REM'. The 'MI\_REM' path includes a 'Delay MI' step and a 'Stop HO timer' input symbol. Both paths converge to a final circle with an 'X' symbol. The text 'G.7042/Y.1305(06)\_FA.9' is located next to the final symbol. + +**Figure A.9/G.7042/Y.1305 – HO procedure** + +NOTE – There are particular circumstances that cause non hitless bandwidth modifications under Hold Off periods. A description of the issue is described in Appendix II. + +## A.5 State diagram for the VCG + +For the whole VCG there is a state machine at the source receive side that would be in one of the following two states: + +- 1) Process MST: The MST information received from one of the members will be processed and distributed to the individual members. +- 2) Wait for RS-Ack: One or more of the Source side member state machines has indicated that a change in sequence numbering has occurred. MST processing is stopped until the Sink confirms receipt by sending RS-Ack, or the RS-Ack timer expires. + + + +State diagram of a VCG with n provisioned members at the receiving Source side + +for each bit(i) in the MST field send ROK/FAIL to member(i) + +G.7042/Y.1305(06)\_FA.10 + +State diagram for the VCG source side receive state machine. It starts at 'Start' and enters 'process MST'. From 'process MST', it can send 'S\_RSQ' (starting timer 'T\_start') or receive 'R\_MST' (leading to 'MST disassemble'). 'MST disassemble' leads to multiple 'R\_x' states, with a note: 'for each bit(i) in the MST field send R\_OK/FAIL to member(i)'. Both 'T\_start' and the 'R\_x' states lead to 'wait for RS-Ack'. From 'wait for RS-Ack', it can encounter 'T\_expiry' (starting 'T\_stop'), receive 'R\_ACK', send 'S\_RSQ' (starting 'T\_restart'), or receive 'R\_MST'. 'T\_stop' and 'T\_restart' lead back to 'process MST', while 'R\_ACK' and 'R\_MST' lead back to 'Start'. + +Figure A.10/G.7042/Y.1305 – Source side VCG receive state diagram + +For the whole VCG there is a state machine at the sink transmit side that has a single state: + +- 1) Assemble MST: The MST information received from each of the members collected in the MST multiframe that is transmitted on all members. A change in sequence numbering detected by one or more of the members will be transmitted to the source side. + + + +The diagram illustrates the sink side VCG transmit state machine. It begins with a 'Start' oval leading to an 'assemble MST' oval. From this oval, a line branches to a bus. On the left, a trapezoidal block labeled $S_{RSQ}$ is connected to the bus, with a double-lined block labeled $R_{ACK}$ below it. On the right, a series of trapezoidal blocks labeled $R_x$ are connected to the bus. Below these $R_x$ blocks is a rectangular block labeled 'assemble MST'. A dashed line from this block points to a note: 'for each member(i) place $R_{OK/FAIL}$ in bit(i) of the MST field sent'. Below the 'assemble MST' block is a double-lined block labeled $R_{MST}$ . A line from $R_{MST}$ loops back to the initial line before the first 'assemble MST' oval. A text box in the top right corner contains the text: 'State diagram of a VCG with n provisioned members at the transmit Sink side'. The diagram is labeled 'G.7042/Y.1305(06)\_FA.11' at the bottom right. + +Sink side VCG transmit state diagram + +Figure A.11/G.7042/Y.1305 – Sink side VCG transmit state diagram + +# Appendix I + +## LCAS Time Sequence Diagrams + +## I.1 Nomenclature + +| | | +|-------|--------------------------------------------| +| LCASC | Link Capacity Adjustment Scheme Controller | +| NMS | Network Management System | +| Sk | Sink (receiving end) | +| So | Source (transmitting end) | + +## I.2 Numbering system + +Members in a virtually concatenated group shall be numbered 0 to $(n - 1)$ , where $n$ = total number of members in the group. + +## I.3 Provisioning + +When a new container is provisioned to be a member of the group, it must be allocated as follows: + +- a) CTRL = IDLE (this code indicates that it is not yet in service). +- b) SQ = Set to a value larger than the currently highest sequence number that has EOS in the CTRL code. The SQ shall not be interpreted while CTRL = IDLE (not yet in service). It is recommended to set SQ to the highest possible value. Because this highest value is technology dependent, it is not possible to indicate a precise value. In the following examples, the value (max) is used to indicate this highest value. +- c) GID = The group ID for that virtually concatenated group. +- d) MST = 1 (FAIL = 1; OK = 0). + +## I.4 Commands + +### I.4.1 Increase bandwidth of VCG (ADD command) + +#### I.4.1.1 Add: (ADD) multiple after last member + +(Example: Add two members after last one in the group of $n$ .) + + + +G.7042/Y.1305(06)\_FI.1 + +Sequence diagram showing the interaction between NMS, LCAS So, mem\_{n-1}(EOS) Sk, mem\_a(new) Sk, and mem\_{a+1}(new) Sk. The diagram illustrates the steps for adding multiple members, including Add Cmdn, CTRL = ADD, MST = OK, CTRL = NORM, CTRL = EOS, and RS-Ack inverted messages. A connectivity check is performed between mem\_a(new) Sk and mem\_{a+1}(new) Sk. + +| Note | | Member n | | | Member a (new) | | | Member a + 1 (new) | | | RS-Ack | +|------|-----------------------------------------------------------------------------------|----------|-------|-----|----------------|-------|------|--------------------|-------|------|--------| +| | | CTRL | SQ | MST | CTRL | SQ | MST | CTRL | SQ | MST | | +| 1 | Initial Condition | EOS | n - 1 | OK | IDLE | (max) | FAIL | IDLE | (max) | FAIL | 0 | +| 2 | NMS issues Add command to So and Sk LCASC | EOS | n - 1 | OK | IDLE | (max) | FAIL | IDLE | (max) | FAIL | 0 | +| 3 | So (a) sends CTRL = ADD and SQ = n;
So (a + 1) sends CTRL = ADD and SQ = n + 1 | EOS | n - 1 | OK | ADD | n | FAIL | ADD | n + 1 | FAIL | 0 | +| 4 | Sk (a + 1) sends MST = OK to So | EOS | n - 1 | OK | ADD | n | FAIL | ADD | n + 1 | OK | 0 | +| 5 | So (n - 1) sends CTRL = NORM;
So (a + 1) sends CTRL = EOS and SQ = n | NORM | n - 1 | OK | ADD | n + 1 | FAIL | EOS | n | OK | 0 | +| 6 | RS-Ack bit inverted due to change in sequence | NORM | n - 1 | OK | ADD | n + 1 | FAIL | EOS | n | OK | 1 | +| 7 | Sk (a) sends MST = OK to So | NORM | n - 1 | OK | ADD | n + 1 | OK | EOS | n | OK | 1 | +| 8 | So (a) sends CTRL = EOS;
So (a + 1) sends CTRL = NORM | NORM | n - 1 | OK | EOS | n + 1 | OK | NORM | n | OK | 1 | +| 9 | RS-Ack bit inverted due to change in sequence | NORM | n - 1 | OK | EOS | n + 1 | OK | NORM | n | OK | 0 | + +NOTE 1 – The example shows new member (a + 1) responding with MST = OK before new member a. This is arbitrary and the first member to respond with MST = OK shall be allocated the SQ = n, then the next new member to respond with MST = OK shall be allocated SQ = n + 1, etc. If for any reason a member being added does not respond with MST = OK within the time-out period, then the So LCASC may report a fail for that member. + +NOTE 2 – The '0' initial value for RS-Ack has been chosen arbitrarily. Only the toggling of the RS-Ack bit is relevant in the example. + +**Figure I.1/G.7042/Y.1305 – ADD multiple members** + +### I.4.2 Decrease bandwidth of VCG (REMOVE command) + +#### I.4.2.1 Decrease: (REMOVE) planned multiple NOT including last member + +(Example: Remove members 4 and 5 from a VCG with n = 6 members.) + + + +Sequence diagram showing the removal of members 4 and 5 from a VCG. The diagram illustrates the interaction between the NMS, So LCASC, and Sk LCASC for members 4, 5, and 6. The NMS sends a 'Decrease cmnd' to the So LCASC. The So LCASC sends 'CTRL = IDLE, SQ = (max)' to members 4 and 5, and 'CTRL = EOS, SQ = 3' to member 6. Members 4 and 5 respond with 'MST = FAIL' to the So LCASC. The So LCASC then sends an 'RS-Ack inverted' to the NMS. The NMS then sends another 'Decrease cmnd' to the Sk LCASC. + +G.7042/Y.1305(06)\_FL2 + +| Note | | Member 4 | | | Member 5 | | | Member 6 | | | RS-Ack | +|------|-----------------------------------------------------------------------------------------------------|----------|-------|------|----------|-------|------|----------|----|-----|--------| +| | | CTRL | SQ | MST | CTRL | SQ | MST | CTRL | SQ | MST | | +| 1 | Initial Condition | NORM | 3 | OK | NORM | 4 | OK | EOS | 5 | OK | 0 | +| 2 | NMS issues Decrease command to So LCASC | NORM | 3 | OK | NORM | 4 | OK | EOS | 5 | OK | 0 | +| 3 | So (3) sends CTRL = IDLE, SQ = (max)
So (4) sends CTRL = IDLE, SQ = (max)
So (5) sends SQ = 3 | IDLE | (max) | OK | IDLE | (max) | OK | EOS | 3 | OK | 0 | +| 4 | Sk (unwanted) sends MST = FAIL to So | IDLE | (max) | FAIL | IDLE | (max) | OK | EOS | 3 | OK | 1 | +| 5 | Sk (unwanted) sends MST = FAIL to So | IDLE | (max) | FAIL | IDLE | (max) | FAIL | EOS | 3 | OK | 1 | +| 6 | RS-Ack bit inverted due to change in sequence | IDLE | (max) | FAIL | IDLE | (max) | FAIL | EOS | 3 | OK | 1 | +| 7 | NMS issues Decrease command to Sk LCASC | IDLE | (max) | FAIL | IDLE | (max) | FAIL | EOS | 3 | OK | 1 | + +Figure I.2/G.7042/Y.1305 – Planned removal of members 4 and 5 out of 6 + +The So LCASC sets CTRL = IDLE on all members to be removed. + +NOTE 1 – CTRL does not change on the other members of the group. + +The example above shows two members being removed with a simultaneous IDLE command from the So LCASC. Reassembly at the Sk ceases to use the 'removed' members immediately upon receipt of the IDLE command. + +The response, however, from the Sk may not be simultaneous. This does not affect the Sk since the IDLE commands will have the same MFI value. The response from the Sk to the So is, of course, simply acknowledgement that the member is no longer in use at the Sk end and the NMS may proceed with de-provisioning of that member, if desired. + +NOTE 2 – The removed members could be de-provisioned as indicated in Note 7 of the table above. + +General rule for SQ adjustment in REMOVE function: + +- 1) All unwanted members are reallocated an SQ greater than the SQ of the member sending the EOS control field, i.e., the highest possible value (max). +- 2) All remaining required members reallocated consecutive SQs (starting from SQ = 0). + +This is best described by the following example: + +| | | | | | | | | | +|--------|----|---|---|-------|-------|---|---|-------| +| | VC | A | B | C | D | E | F | G | +| Before | SQ | 0 | 1 | 2 | 3 | 4 | 5 | 6 | +| | | | | U | U | | | U | +| After | SQ | 0 | 1 | (max) | (max) | 2 | 3 | (max) | + +NOTE 3 – The '0' initial value for RS-Ack has been chosen arbitrarily. Only the toggling of the RS-Ack bit is relevant in the example. + +#### I.4.2.2 Decrease: (REMOVE) planned single last member + + + +The sequence diagram illustrates the interaction for a planned decrease of a single last member. It features four lifelines: NMS, LCAS So, memn-1 Sk, and memn Sk. + +Note 1: Initial state. + +Note 2: NMS sends a 'Decrease cmnd' to LCAS So. + +Note 3: LCAS So sends 'CTRL = EOS, SQ = (n-2)' to memn-1 Sk. memn-1 Sk responds with 'CTRL = IDLE, SQ = (max)'. + +Note 4: memn-1 Sk sends 'RS-Ack inverted' back to LCAS So. + +Note 5: memn-1 Sk also sends 'MST = FAIL' to LCAS So. + +Note 6: NMS sends another 'Decrease cmnd', this time directly to memn Sk. + +The diagram is labeled G.7042/Y.1305(06)\_FI.3. + +Sequence diagram showing the interaction between NMS, LCAS So, mem\_{n-1} Sk, and mem\_n Sk for a planned decrease of a single last member. The diagram includes notes 1-6 and control messages like 'Decrease cmnd', 'CTRL = EOS', 'CTRL = IDLE', 'RS-Ack inverted', and 'MST = FAIL'. + +| Note | | Member n – 1 | | | Member n | | | RS-Ack | +|------|-----------------------------------------------------------------------------|--------------|-------|-----|----------|-------|------|--------| +| | | CTRL | SQ | MST | CTRL | SQ | MST | | +| 1 | Initial Condition | NORM | n – 2 | OK | EOS | n – 1 | OK | 0 | +| 2 | NMS issues Decrease command to So LCASC | NORM | n – 2 | OK | EOS | n – 1 | OK | 0 | +| 3 | So (unwanted) sends CTRL = IDLE, SQ = (max);
So (n – 2) sends CTRL = EOS | EOS | n – 2 | OK | IDLE | (max) | OK | 0 | +| 4 | RS-Ack bit inverted, due to a change in the sequence | EOS | n – 2 | OK | IDLE | (max) | FAIL | 1 | +| 5 | At the same time Sk (unwanted) sends MST = FAIL | EOS | n – 2 | OK | IDLE | (max) | FAIL | 1 | +| 6 | NMS issues Decrease command to Sk LCASC | EOS | n – 2 | OK | IDLE | (max) | FAIL | 1 | + +Figure I.3/G.7042/Y.1305 – Planned decrease single (last) member + +NOTE 1 – The removed member could be de-provisioned as indicated in Note 6 of the table above. + +NOTE 2 – MST value should be updated at the latest in the same control packet sending the RS-Ack toggled. + +NOTE 3 – The '0' initial value for RS-Ack has been chosen arbitrarily. Only the toggling of the RS-Ack bit is relevant in the example. + +### I.4.3 Decrease bandwidth of VCG due to fault (DNU command) + +#### I.4.3.1 Decrease (DNU) due to fault single (last) member + + + +| Note | | Member n - 1 | | | Member n (EOS) | | | RS-Ack | +|------|------------------------------------------------------|--------------|-------|-----|----------------|-------|------|--------| +| | | CTRL | SQ | MST | CTRL | SQ | MST | | +| 1 | Initial Condition | NORM | n - 2 | OK | EOS | n - 1 | OK | 0 | +| 2 | Sk (fault_mem) sends MST = FAIL to So | NORM | n - 2 | OK | EOS | n - 1 | FAIL | 0 | +| 3 | So (fault_mem) sends DNU; So (fault_mem-1) sends EOS | EOS | n - 2 | OK | DNU | n - 1 | FAIL | 0 | +| 4 | See text below table | EOS | n - 2 | OK | DNU | n - 1 | FAIL | 0 | +| 5 | See text below table | EOS | n - 2 | OK | DNU | n - 1 | FAIL | 0 | +| 6 | Network Fault cleared MST = OK sent to So | EOS | n - 2 | OK | DNU | n - 1 | OK | 0 | +| 7 | CTRL changed from DNU to NORM | NORM | n - 2 | OK | EOS | n - 1 | OK | 0 | + +Sequence diagram showing the decrease of bandwidth due to a fault in the single (last) member. The diagram illustrates the interaction between NMS, LCAS So, mem\_{n-1} Sk, and mem\_n(EOS) Sk. The sequence of events is: 1. Initial Condition: All members are OK. 2. Fault occurs at mem\_n(EOS) Sk. 3. mem\_n(EOS) Sk sends MST = FAIL to So. 4. So sends CTRL = EOS to mem\_{n-1} Sk. 5. So sends CTRL = DNU to mem\_n(EOS) Sk. 6. Network fault is cleared. 7. mem\_n(EOS) Sk sends MST = OK to So. 8. So sends CTRL = NORM to mem\_{n-1} Sk. 9. So sends CTRL = EOS to mem\_n(EOS) Sk. The diagram includes seven notes: Note 1 (Initial Condition), Note 2 (Sk (fault\_mem) sends MST = FAIL to So), Note 3 (So (fault\_mem) sends DNU; So (fault\_mem-1) sends EOS), Note 4 (See text below table), Note 5 (See text below table), Note 6 (Network Fault cleared MST = OK sent to So), and Note 7 (CTRL changed from DNU to NORM). The diagram is labeled G.7042/Y.1305(06)\_FI.4. + +Figure I.4/G.7042/Y.1305 – Decrease due to network fault, single (last) member + +The So LCASC sets CTRL = DNU on faulty member, and sets CTRL = EOS on preceding member. + +*Text referring to Note 3 of the table above* + +Even though a change has been made to the bandwidth and to which member contains the EOS, this change is a temporary change and does not trigger an RS-ACK. + +*Text referring to Note 4 of the table above* + +- As soon as an MSU\_L is detected, the Sk will immediately begin reassembly of the concatenated group using only the NORM and EOS members. For a time (propagation time from Sk to So + reaction time of the So + propagation time from So to Sk), the reassembled data will be erroneous because it is sent on all members as per pre-fault. +- If a TSD is detected, the Sk continues to use the payload of this member. The bit errors in the payload area of the member have to be handled by the server to client adaptation function at the sink side of the VCG. For a time (propagation time from Sk to So + reaction time of the So + propagation time from So to Sk), the reassembled data will be erroneous because it is sent on all members as per pre-fault. + +Text referring to Note 5 of the table above + +However, the So will stop sending data on the erroneous members (since they will have been reported back as MST = FAIL and consequently set the failed member to DNU), and send data only on the remaining NORM and EOS members. + +- In case of MSU\_L: From the time the CTRL = DNU would have arrived at the Sk until the CTRL = NORM is received again, the bandwidth of the VCG is reduced. +- In case of TSD: From the time the CTRL = DNU arrives at the Sk, the bandwidth of the VCG is reduced. + +Text referring to Note 7 of the above table + +When the failed member is repaired, the CTRL is changed to NORM from DNU. The Sk will then use this member's payload again to reassemble the data. + +NOTE 1 – If the failed channel is subsequently deleted through a planned decrease prior to the fault clearing, the Sk will not be able to see the change in the failed member's control packet. As a result, RS-Ack will not be inverted by this planned decrease and the So has to rely on the RS-Ack timeout to continue processing MST. The bandwidth of the VCG is not affected. + +NOTE 2 – The '0' initial value for RS-Ack has been chosen arbitrarily. Only the toggling of the RS-Ack bit is relevant in the example. + +#### I.4.3.2 Decrease: (DNU) due to fault NOT last member + + + +The sequence diagram illustrates the interaction between the Network Management System (NMS), the LCAS Source (So), and several SK (Sk) members. The timeline is divided into seven notes: + +- Note 1:** Initial state where all members are active (NORM). +- Note 2:** A fault occurs on Member 4. Member 4 Sk sends an MST = FAIL packet to the So. +- Note 3:** The So receives MST = FAIL and sends a CTRL = DNU packet back to Member 4 Sk. The NMS is notified of the failure. +- Note 4:** The So continues to send data, but excludes Member 4 due to the DNU status. +- Note 5:** The fault is cleared. Member 4 Sk sends an MST = OK packet to the So. +- Note 6:** The So receives MST = OK and changes the control status for Member 4 back to NORM. +- Note 7:** The So sends a CTRL = NORM packet to Member 4 Sk, restoring full bandwidth. + +Sequence diagram showing network fault and recovery for a single member (Member 4). The diagram includes lifelines for NMS, LCAS So, mem2 Sk, mem3 Sk, mem4 Sk, and mem5(EOS) Sk. It illustrates the flow of MST and CTRL packets during a fault and subsequent recovery, with notes 1-7 explaining the events. + +G.7042/Y.1305(06)\_FI.5 + +| Note | | Member 2 | | | Member 3 | | | Member 4 | | | Member 5 (EOS) | | | RS-Ack | +|------|-------------------------------------------|----------|----|-----|----------|----|-----|----------|----|------|----------------|----|-----|--------| +| | | CTRL | SQ | MST | CTRL | SQ | MST | CTRL | SQ | MST | CTRL | SQ | MST | | +| 1 | Initial Condition | NORM | 1 | OK | NORM | 2 | OK | NORM | 3 | OK | EOS | 4 | OK | 0 | +| 2 | Sk (fault mem) sends MST = FAIL to So | NORM | 1 | OK | NORM | 2 | OK | NORM | 3 | FAIL | EOS | 4 | OK | 0 | +| 3 | So (fault mem) sends CTRL = DNU | NORM | 1 | OK | NORM | 2 | OK | DNU | 3 | FAIL | EOS | 4 | OK | 0 | +| 4 | See text below table | NORM | 1 | OK | NORM | 2 | OK | DNU | 3 | FAIL | EOS | 4 | OK | 0 | +| 5 | See text below table | NORM | 1 | OK | NORM | 2 | OK | DNU | 3 | FAIL | EOS | 4 | OK | 0 | +| 6 | Network Fault cleared MST = OK sent to So | NORM | 1 | OK | NORM | 2 | OK | DNU | 3 | OK | EOS | 4 | OK | 0 | +| 7 | CTRL changed from DNU to NORM | NORM | 1 | OK | NORM | 2 | OK | NORM | 3 | OK | EOS | 4 | OK | 0 | + +Figure I.5/G.7042/Y.1305 – Decrease due to network fault, single (not last) member + +*Text referring to Note 4 of the table above* + +- As soon as an MSU\_L is detected, the Sk will immediately begin reassembly of the concatenated group using only the NORM and EOS members. For a time (propagation time from Sk to So + reaction time of the So + propagation time from So to Sk), the reassembled data will be erroneous because it is sent on all members as per pre-fault. +- If a TSD is detected, the Sk continues to use the payload of this member. The bit errors in the payload area of the member have to be handled by the server to client adaptation function at sink side of the VCG. For a time (propagation time from Sk to So + reaction time of the So + propagation time from So to Sk), the reassembled data will be erroneous because it is sent on all members as per pre-fault. + +*Text referring to Note 5 of the table above* + +However, the source will stop sending data on the erroneous members (since they will have been reported back as MST = FAIL and consequently set the failed member to DNU), and send data only on the remaining NORM and EOS members. + +- In case of MSU\_L: From the time the CTRL = DNU would have arrived at the Sk until the CTRL=NORM is received again, the bandwidth of the VCG is reduced. +- In case of TSD: From the time the CTRL = DNU arrives at the Sk, the bandwidth of the VCG is reduced. + +*Text referring to Note 7 of the above table* + +When the failed member is repaired, the CTRL is changed to NORM from DNU. The Sk will then use this member's payload again to reassemble the data. + +NOTE – The '0' initial value for RS-Ack has been chosen arbitrarily. Only the toggling of the RS-Ack bit is relevant in the example. + +# Appendix II + +## Non-hitless bandwidth modifications during Hold Off periods + +## II.1 Introduction + +SDL diagram for the Hold Off procedure described in A.4.4 shows the occurrence of the sole MI-REMOVE command as a possible input signal, causing other inputs, not explicitly depicted, to be discarded. The LCAS state machine will therefore not act on CTRL words received during the hold-off periods, thus impacting the traffic. + +## II.2 Removal of a group member at Source + +The removal action at source does not require synchronization between source and sink state machines and is therefore already performed at the source before signalling the change to the sink. Since the source already excluded the member from carrying payload, the sink should be able to react to this change immediately, even if it is currently in the hold-off state. If not, client payload will be lost until the timer expires. + +## II.3 TSD conditions raised while performing ADD commands + +When performing a member's addition, at Sink a CTRL = ADD is received. Sink state will therefore move to the OK state and signal MST = OK to the source. The source will then move the member to the NORM state, signals CTRL = NORM/EOS and starts sending payload on this member. If meanwhile TSD is raised at the sink, the sink will have started a hold-off timer and is not able to react to the CTRL = NORM/EOS. Client payload will be lost until the timer expires. + +## II.4 Enhanced HO procedure + +Even if the above-mentioned events are very limited in time and are characterized by a very low probability of occurrence, the HO procedure described in A.4.4 could optionally be enhanced in order to allow hitless capacity adjustments also in particular cases affected by transmission errors. The HO procedure SDL diagram to override the issue is reported below. + + + +``` + +stateDiagram-v2 + [*] --> HO_procedure : HO procedure + HO_procedure --> Start_HO_timer : Start HO timer + Start_HO_timer --> Wait_for_time_out : Wait for time-out + Wait_for_time_out --> HO_timer_expired : HO timer expired + Wait_for_time_out --> MI_REM : MI_REM + Wait_for_time_out --> F_IDLE : F_IDLE + Wait_for_time_out --> F_NORM_EO : F_NORM/EO + F_NORM_EO --> F_was_ADD{F was ADD?} + F_was_ADD -- No --> Wait_for_time_out + F_was_ADD -- Yes --> Delay_F_NORM_EO : Delay F_NORM/EO + HO_timer_expired --> Stop_HO_timer + MI_REM --> Delay_MI : Delay MI + F_IDLE --> Delay_F_IDLE : Delay F_IDLE + Delay_F_NORM_EO --> Stop_HO_timer + Delay_MI --> Stop_HO_timer + Delay_F_IDLE --> Stop_HO_timer + Stop_HO_timer --> [*] + +``` + +SDL diagram for the Hold Off procedure. It starts with 'HO procedure' (state), followed by 'Start HO timer' (action). Then 'Wait for time-out' (state). From there, it branches into four conditions: 'HO timer expired' (event), 'MI\_REM' (event), 'F\_IDLE' (event), and 'F\_NORM/EO' (event). The 'F\_NORM/EO' event leads to a decision 'F was ADD?'. If 'No', it loops back to 'Wait for time-out'. If 'Yes', it leads to 'Delay F\_NORM/EO' (action). All four events lead to a common junction point. The 'MI\_REM', 'F\_IDLE', and 'F\_NORM/EO' paths include delay actions: 'Delay MI', 'Delay F\_IDLE', and 'Delay F\_NORM/EO' respectively. All three delay actions lead to a common junction point. From this junction, the flow goes to 'Stop HO timer' (action), which then leads to a final state symbol (circle with an X). A label 'G.7042/Y.1305(06)\_FI-1' is present near the bottom right. + +Figure II.1/G.7042/Y.1305 – Optionally enhanced Hold Off procedure SDL diagram + +# 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.764-199012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.764-199012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..422f8e241d2880c8e68e3e94b869d6a0f9427bdf --- /dev/null +++ b/marked/G/T-REC-G.764-199012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d63d12739a0bfa782391eb486074787d3c8a61e302171c075c34cc9ff870280 +size 7517 diff --git a/marked/G/T-REC-G.764-199012-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/G/T-REC-G.764-199012-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd768671532a4cf472fcfc66d6a677783bac3dc4 --- /dev/null +++ b/marked/G/T-REC-G.764-199012-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df99fff3aa6deb3159e445b67e7881331061ceb485226a45ca69a5de5cde2031 +size 31671 diff --git a/marked/G/T-REC-G.764-199012-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/G/T-REC-G.764-199012-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2dcd253a8c0ad6f0e52fe9de8f74114eef680ca6 --- /dev/null +++ b/marked/G/T-REC-G.764-199012-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f93b775ea48ce252912b8f0fe23e52b0c3fd77ea94a7c962a6eb1e81b63b3394 +size 5449 diff --git a/marked/G/T-REC-G.764-199012-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/G/T-REC-G.764-199012-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82207a3b80d163d2d3bd1ba1e8a8da1155fed63d --- /dev/null +++ b/marked/G/T-REC-G.764-199012-I_PDF-E/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb27aea9addbe06755713e14cd1ea46f9a3200e522f37476ce6aeb893828dc00 +size 6581 diff --git a/marked/G/T-REC-G.764-199012-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.764-199012-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0111a11eb56c80b1e951095839761904641cb248 --- /dev/null +++ b/marked/G/T-REC-G.764-199012-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18ac42a15f0fba08da190ae1f7f20f683492e0bdc240a7eb54a9f755eead209e +size 52961 diff --git a/marked/G/T-REC-G.764-199012-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/G/T-REC-G.764-199012-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..336d0f06517b28417bc7c5b6f9c57f20074de219 --- /dev/null +++ b/marked/G/T-REC-G.764-199012-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c260619d1e5a91bb6e46a850308fb8522983f035b09a16fb7860a6233a137650 +size 61649 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a5a8b647e62953c814605fae16e2974dbd6636b --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1da57f8baa1ab8d5e5c52dc7057a0639506ee07bc6cbad195179e8ba22c8db34 +size 18748 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e32f9b8f1141bed243c16e02a6cd1411cbb87f1 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c395c4bbde83b1e232652a43f51538278c116f51f710c37e20a073f7333726c8 +size 6134 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b905bb6920f285821fcbcbd0a5367ff058d4c03 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91dcddaebae439f8301df48f67fbcf36779995b9d351cfbc7c7a041817430c62 +size 94148 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74bb4a6ed99272237c9235f89d9a0aeaa269b5ab --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21137f741862e477231f97455b39e0e456c768b41bca6d0b38be61556c42ac74 +size 54607 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91d089a8419726a4b0e16c47339b32b43e1666aa --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:133801dbedc3fbe68153d98c91c5220f1ad165881a668384769466c5d660e0af +size 43404 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a93d3c8be01466e310aafe2a09eb669121c458b8 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:354910d44f789246a81b1b1d0f6e17170a9a4a8718a6adfd77100b684ae3f3d3 +size 55179 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..244d4b71ac3562caac0d4c9fcab0b2ab9520a5df --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad22d6e0faa6f0de7e531cf6f267665ad87078b6bf98650dcf033b995d1b9de2 +size 58215 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23e30ce2a92b1ee9987d4dab11813e9bbeb838d6 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2921c18e3572608df28f434324b986130c79292ead3349b6f35f71fc4530241b +size 33880 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5b0033656e6586e5142bac70bba9e47c89ca597 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1655a014108fe2df31293078bff33070ac9d0254849445f5343fc08547e41074 +size 146345 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..133d594ab37c1d941f8dd75d63d20d5d03d033e7 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e908823cd956322908367c133df4cee5bcc8f75e0517dbbcb0b1cb09fcb7cf4e +size 21569 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7a9bda08ca4c2455503aa3c4feedbe0cf0496e7 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b52216b7ad3ded6ce68c607dd18a23fccfbce5ef2cfdbfe7054969a0f78813fd +size 87867 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30b5aa9695243cd40267ae0d1c75e1de4c265599 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ee86e6608e4b825b78f36a5332673568a71ace43229c781807c06e504f1421d +size 26219 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2133783b5af7082647b3ba94f143ed90cdef95c --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aab3e70c97c731461fdad415e6affc2a6ea6b9093d0a4247a5832246f7cc9865 +size 118677 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0fa64b7c8f05b4fc32d0a1c0b56943afbd810a6 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:827480b4b6a3246b060616b83b83ac7eaf7fa4b70be877576425d0428847cc4e +size 26073 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7957d173a3738a276d878e4b835eb26bd4140ec --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4fe44d859c39a200394c09573e4d0cd1e554af6b953524104022899665e0b60 +size 42206 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/b58cedaf15ad4f0edee5621820865ccc_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/b58cedaf15ad4f0edee5621820865ccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baccd31fb9348ddf93913441d3a5d6b5d49c9676 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/b58cedaf15ad4f0edee5621820865ccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51925702163ada61266a63d28127443b601eff272c82fd506e217458494a9f65 +size 25403 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d43139ca511a6216e63998b1deee3b43f9d6af09 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f2cacf4ba8d9aa5bf8f682b91641b8fca1a0adfd4f356dedcd4db82f61a0c8c +size 26196 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/b6b53a74ad203c01b81e5427e9d6a898_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/b6b53a74ad203c01b81e5427e9d6a898_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59c8cc90a826922e8f078162b9fe2eacc7f0dfa5 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/b6b53a74ad203c01b81e5427e9d6a898_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fc3fdd4067ac49ecdcf05b366f522e0800f95818289a6a14f189f2c0eaa9b1f +size 15450 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..039dab786680366f9615c1862e0d34bf6e44f9b0 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcaec836ad540ca8656d652987007eac94c561d16f82e78d0155a447fdb4cda8 +size 59745 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.7702-202204-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58fb632f3aa9f169f486362dc5f0ec5c642f1025 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eacf92cdbba97d63860dc317f62b3867d37774a72e92e6f8703d0721f9ffce8c +size 81434 diff --git a/marked/G/T-REC-G.7702-202204-I_PDF-E/raw.md b/marked/G/T-REC-G.7702-202204-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e332db08c6d6942b6817c944008571a43c5d62c1 --- /dev/null +++ b/marked/G/T-REC-G.7702-202204-I_PDF-E/raw.md @@ -0,0 +1,1120 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.7702** + +(04/2022) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Data over Transport – Generic aspects – Transport +network control aspects + +# --- **Architecture for SDN control of transport networks** + +Recommendation ITU-T G.7702 + +## 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.* + +## Recommendation ITU-T G.7702 + +# Architecture for SDN control of transport networks + +## Summary + +Recommendation ITU-T G.7702 describes the reference architecture for software defined networking (SDN) control of transport networks applicable to both connection-oriented circuit and/or packet transport networks. This architecture is described in terms of abstract components and interfaces that represent logical functions (abstract entities versus physical implementations). + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.7702 | 2018-03-16 | 15 | 11.1002/1000/13540 | +| 2.0 | ITU-T G.7702 | 2022-04-06 | 15 | 11.1002/1000/14929 | + +## Keywords + +Application of SDN to transport networks, control plane interface (CPI), management-control system (MCS), MC components, transport SDN. + +--- + +\* To access the Recommendation, type the URL
An optional ordered list of SNP pairs. | A subnetwork connection (controller response with the established connection) | +| Output interface | Basic output parameters | Basic return parameters | +| Connection request out | Boundary resource identifier,
Ordered list of SNP pairs | An ordered list of pairs of SNPs | + +### 8.3.2 Connection controller (CC) component + +The common description for the CC component is provided in clause 8.3.2 of [ITU-T G.7701]. + +In an SDN controller the CC establishes and releases connections on VNs within a client context. Information the CC may need about links such as utilization, is maintained in the resource database (RDB). If an ordered list of SNP pairs is supplied by an NCC when requesting a connection, these are used in the request to the routing controller (RC) for resolution of the route. Connections established and their associated identifiers, are CC artifacts that are also maintained in the RDB. + +For the 1:n case of SDN controllers that use the NCC to NCC interfaces, the CC's behaviour is similar to that in the hierarchical routing case. The single client NCC makes multiple NCC calls to the 'n' servers and gathers a pair of SNPs per call. Each SNP pair represents the returned connection. At the client NCC, the pairs need to be concatenated and it is the connection controller (CC) that does this. The Connection request out interface from the NCC described in clause 8.3.1 includes an ordered list of subnetwork connection (SNC) pairs that the client CC uses when constructing the connection. + +### 8.3.3 Routing controller (RC) component + +The common description for the RC component is provided in clause 8.3.3 of [ITU-T G.7701]. + +In an SDN controller, the RC component computes routes based on the resources in the client's VN. It maintains topology information that is logically in the RDB and the relationship between a VN and its underlying topologies in server contexts. + +### 8.3.4 Link resource manager (LRM) component + +The common description for the link resource manager (LRM) is provided in clause 8.3.4 of [ITU-T G.7701]. + +In [ITU-T G.7703] and [ITU-T G.7701] a different LRM is responsible for each end (LRMA, LRMZ) of an SNPP link. A logically centralized controller found in SDN has a global view of resources in the network. As a result, the LRM in an SDN controller covers both A and Z scope of SNPP links in the SDN control domain. For those SNPP links between SDN control domains, the LRM only covers the A or Z end in scope. + +### **8.3.5 Discovery agent (DA) component** + +The common description for the discovery agent (DA) component is provided in clause 8.3.5 of [ITU-T G.7701]. + +### **8.3.6 Termination and adaptation performer (TAP) component** + +The common description for the termination and adaptation performer (TAP) component is provided in clause 8.3.6 of [ITU-T G.7701]. + +### **8.3.7 Directory service (DS) component** + +The common description for the directory service (DS) component is provided in clause 8.3.7 of [ITU-T G.7701]. + +The DS component may also be used by other components when mapping between local topology and underlying topology information in server contexts. + +### **8.3.8 Notification component** + +The common description for the notification component is provided in clause 8.3.8 of [ITU-T G.7701]. + +A transport resource (e.g., a link) may contribute to many VNIs and some of the contexts associated with those VNIs may subscribe to a type of notification regarding that resource (e.g., an alarm). When a change occurs that is cause for notification, the responsible MC component in each of the affected contexts recognizes the change and generates the appropriate notification(s). + +### **8.3.9 Protocol controller (PC) component** + +The common description for the protocol controller component appears in clause 8.3.9 of [ITU-T G.7701]. + +The protocol controller maps the parameters of the abstract interfaces of the MC components into messages that are carried by a protocol to support interconnection via an interface. + +### **8.3.10 Traffic policing (TP) component** + +The common description for the traffic policing component is provided in clause 8.3.10 of [ITU-T G.7701]. + +This traffic policing component's role is to check that the incoming user connection is sending traffic according to the parameters agreed upon. + +# **9 Control communications network** + +The application of SDN to transport network requires a control communications network (CCN) to transfer information e.g., between SDN controllers at different levels, between SDN controller and the resources in their scope, or between SDN controllers and their management functions. The CCN is supported by the DCN functions specified in [ITU-T G.7712]. + +The CPI and management and control interface (MCI) are the interfaces defined for these information transfers; the information transfers themselves require a CCN between the communicating entities. + +The information transported via different instances of the CPI and MCI varies e.g., it may relate to connectivity, compute requirements, dimensioning, reliability, performance, security, etc. + +The reliability and security required from the CCN may vary depending on particular usage. Appropriate implementation mechanisms should be used to support reliable information transfer in the CCN if that is required. The CCN should provide appropriate security in terms of access control and guaranteeing secure transport of information. Mechanisms such as authentication, authorization + +and accounting (AAA) and transport layer security (TLS) may be appropriate solutions to those challenges. + +Several different communication scenarios and how some aspects of the communication vary between them are examined below: + +## **Control communication network between controller and transport resources:** + +- The information carried over the interface between controller and resources in its scope is used for topology discovery, path computation, connectivity control and maintenance purposes. +- Controllers establish resource topology by processing adjacency information provided by those resources. +- A controller processes a connection request from one of its clients by establishing the required path and then sending configuration commands to the appropriate resources on that path. +- Resources can communicate changes in their state to the controller, which, for example, provides the information for network or service monitoring applications. + +## **Control communication network between controllers at different levels:** + +- Services are established across a network by the appropriate and coordinated configuration of the resources in the scope of one or more controllers. +- Information is communicated between controllers to coordinate this resource configuration. For example, signalling messages exchanged between NCCs and the routing information exchanged between RCs, are transported over the interface between controllers at different levels allowing the coordination of network configuration that establishes service for the client. + +## **Control communication network between SDN controllers and management applications:** + +The information transferred over the interface in this scenario is related to fault, configuration and performance management of the controller. Management applications are concerned with the control, surveillance and performance of the controller. + +A controller which suffers from fault may be replaced with the auxiliary one according to the configuration of management functions once the fault is detected. + +Performance information from the controller, such as congestion control should be reported to or can be acquired by the management application through the control communication network. + +# **10 Management aspects** + +This clause deals only with management of SDN controllers themselves. Management of resources controlled by the controller and management of SDN applications themselves are out of scope of this Recommendation. In general, the customer of a transport network operator may interact with the network using an SDN application. It is a local matter for such applications to deal with details of customer management (authorization, billing, reporting, etc.). The application may use information obtained from its interaction with the SDN controller e.g., when it invoked a call setup and for whom, to generate billing and reporting details, etc. + +## **10.1 Management of SDN controllers** + +The SDN controllers should support configuration management, fault management, performance management and security management for the SDN controllers, including: + +- The initial parameters configuration for controllers, e.g., the address, name ID, client-server relationships, enable and disable, etc. + +- The status management of controllers themselves, including the process status of software and hardware, the usage status of controllers' resources, operating and running status and management status. +- The alarms and events management of controllers, e.g., the node failure, the modules or components failure, the process failure of software and hardware, etc. +- The performance management of controllers, e.g., the configuration of reports for performance monitoring, the performance of controlling process, the running performance of controllers' resources, etc. +- The policy management for controllers, including the mapping policy for quality of service (QoS), the restriction policy for routing, the security policy, the policy of protection and restoration, etc. + +## 10.2 Management of control plane interfaces (CPI) + +The management aspects of control plane interfaces include the management of CPI illustrated in Figure 6-2, which include: + +- The type of interface, the type of interface protocol, address, identifier, etc. +- The type of SDN control signalling protocol and related parameters, etc. +- Access control and related policy management of CPI, including access user management, e.g., creation access username and password, access authority, access security policy, etc. + +## 10.3 Management of control communication network (CCN) + +The management aspects of CCN include: + +- The CCN configuration management, including CCN channels, interface address and identifier, transport mode, protection and restoration, etc. +- The status monitoring of CCN, including alarms (e.g., the communication failure between controllers or other planes), performance, etc. + +# 11 Identifiers + +A number of distinct and independent sets of name spaces, from which identifiers are drawn are described in clause 11 of [ITU-T G.7701]: + +- Resources in the transport network; +- Control view of transport resources; +- MC components; +- Control artifacts; +- Reference points; +- Control communications network. + +Each of these name spaces and the identifiers that are drawn from them is described in clause 11 of [ITU-T G.7701]. Further information on the use of these name spaces and identifiers in the context of SDN is provided in the remainder of this clause. + +## 11.1 Resources in the transport network + +The identifiers used for the resources in the transport network are described in clause 11.1 of [ITU-T G.7701]. + +The only SDN components that use these identifiers are the DA and TAP. + +## 11.2 Control view of transport resources + +The name spaces used to provide a control view of transport resources are described in clause 11.2 of [ITU-T G.7701]. + +## 11.3 MC components + +The name spaces used for MC components are described in clause 11.3 of [ITU-T G.7701]. + +## 11.4 Control artifacts + +As described in clause 11.4 of [ITU-T G.7701], the MC components create and use control artifacts including, for example, connections, routes and calls. Normally the control component that creates a control artifact assigns an identifier. These identifiers are drawn from an independent name space. + +## 11.5 Reference points + +Reference points are described in clause 11.5 of [ITU-T G.7701]. The following subclauses describe how these reference points are used in SDN. + +### 11.5.1 SDN control plane interfaces + +The SDN control plane interfaces with other entities are shown in Figure 11-1. These interfaces are reference points for information hiding, traffic and namespace isolation and policy enforcement. Reference points of MC components could be bundled in these interfaces. + +The control plane interfaces include: + +- a) The relationships between transport NEs and SDN controllers, between SDN controllers at adjacent levels in a recursive hierarchy (see clause 10) and between SDN controller and applications, are all client and server. North-south instances of these same interfaces with the same set of information models (IMs) are used between each level of the hierarchy and may represent (see clause 7) virtual resources. +- b) In the management-control continuum (MCC), an administration role acts to configure and manage SDN controllers. The interface between a SDN controller and the administration role is an MCI – see Figure 11-1. Note that the administration role may be implemented in a legacy management system (e.g., EMS/OSS/BSS). + + + +The diagram illustrates the general architecture of SDN controller interfaces. A central blue rectangular box is labeled "SDN controller". To its left, a white rounded rectangular box labeled "Administration role" is connected via a horizontal yellow double-headed arrow labeled "MCI". Above the SDN controller, a green double-headed arrow labeled "CPI" connects to the text "Client". Below the SDN controller, another green double-headed arrow labeled "CPI" connects to the text "Server". At the bottom right of the diagram, the text "G.7702(22)\_F11-1" is present. + +Diagram of SDN controller interfaces showing an Administration role connected via an MCI interface, and a Client and Server connected via CPI interfaces. + +**Figure 11-1 – General architecture of SDN controller interfaces** + +Figure 11-2 shows a 1:1 hierarchical stack of controllers at different levels. The control function inside the transport NE could be seen as a management and control agent of SDN in the NE. + +Note that in Figure 11-2 the N+2 level controller could be an SDN application; the server SDN controller at level N+1 is, however, only aware of the presence of a client, i.e., it cannot distinguish between an application and another SDN controller. + + + +Figure 11-2: 1:1 Hierarchical stack of controllers. The diagram shows a vertical stack of five SDN controllers. From top to bottom, they are labeled 'N + 2 level SDN controller', 'N + 1 level SDN controller', 'N level SDN controller', 'N - 1 level SDN controller', and a combined box for 'Control function Transport network element' and 'Data plane functions'. Each adjacent pair of controllers is connected by a green double-headed arrow labeled 'CPI'. To the left of each controller, a yellow double-headed arrow labeled 'MCI' points to a vertical rounded rectangle labeled 'Administration role'. The bottom-most box is divided into two sections: the top section is 'Control function Transport network element' and the bottom section is 'Data plane functions'. A small text 'G.7702(22)\_F11-2' is at the bottom right. + +**Figure 11-2 – 1:1 Hierarchical stack of controllers** + +Figure 11-3 shows an m:1 hierarchical arrangement of SDN controllers where the server has created separated client contexts for each of its three clients and assigned resources to each of those clients (the resources are visible in the context). This is referred to as 'resource partitioning'. Note that, although the clients of the low level controller are all shown here as SDN controllers, the low level controller can also support applications over the CPI. In general, a controller is unaware of the role or naming convention applied to its CPI clients (see clause 6.4.1). By extension this means that applications can appear as clients of a controller at any level in a hierarchical arrangement of controllers. + + + +Figure 11-3: m:1 hierarchical arrangement of controllers in partitioned view. The diagram shows a 'High level' row of SDN controllers (SDN controller 1, SDN controller 2, ..., SDN controller m) above a single 'Low level SDN controller'. Each high-level controller is connected to the low-level controller by a green double-headed arrow labeled 'CPI'. A small text 'G.7702(18)\_F11-3' is at the bottom right. + +**Figure 11-3 – m:1 hierarchical arrangement of controllers in partitioned view** + +Figure 11-4 shows a 1:n hierarchical arrangement of controllers where the high level controller has established relationships with three server controllers each of which provide it resources. The entire set of resources available to the high level controller are referred to as a 'virtualized view'. + + + +G.7702(18)\_F11-4 + +Figure 11-4: 1:n hierarchical arrangement of controller in virtualized view. A 'High level SDN controller' at the top is connected via green double-headed arrows labeled 'CPI' to multiple 'SDN controller' boxes below (SDN controller 1, SDN controller 2, ..., SDN controller n). + +**Figure 11-4 – 1:n hierarchical arrangement of controller in virtualized view** + +To migrate a transport network to SDN control, one approach is to upgrade the EMS/NMS with the SDN controller function (such as call control and etc.) and a CPI agent, which allows interaction with a higher level SDN controller or application as illustrated in Figure 11-5. The EMS/NMS enhanced with SDN controller functionality could reuse a proprietary interface, or other protocol (e.g., Netconf/YANG) to communicate with the legacy transport network elements which can remain unchanged. + + + +G.7702(22)\_F11-5 + +Figure 11-5: A migration approach to support SDN control for a legacy transport network. Part (a) shows an 'EMS/NMS' box connected to a 'Legacy transport network element' box via a double-headed arrow labeled 'Proprietary interface or other protocol (e.g., Netconf/YANG)'. Part (b) shows the migration: the 'EMS/NMS' is now an 'EMS/NMS updated controller' box containing a 'CPI agent' and 'Call control, etc.' sub-box, and an 'EMS/NMS' sub-box. This updated controller is connected to the 'Legacy transport network element' via the same proprietary interface, and to 'SDN applications or high level SDN controller' via a 'CPI' interface. A large arrow points from (a) to (b). + +**Figure 11-5 – A migration approach to support SDN control for a legacy transport network** + +A boundary resource identifier (BRI) is used to identify both the transport resource(s) and the interface(s) to MC components at the boundary of a domain. The BRI is drawn from an independent name space. The use of an independent name space avoids exposing the identifiers that the MC components use within the domain. + +The CPI between the two SDN controllers shown in Figure 7-3 is an example of an interface that could be identified by a BRI. + +### 11.5.2 Functional requirements for identifiers in the CPI + +The CPI should support several categories of functional requirements, including topology, connection, path computation and resource virtualization/abstraction, performance and fault management, notification/events, etc. + +#### 11.5.2.1 Topology management functions + +The CPI should support the topology management function and retrieval of topological information, which should include: + +- Topology management for intra-domain and multi-layer transport networks; + +- Topology management for inter-domain networks or links; +- Abstraction of topology and resources of transport networks. +- Getting detailed topological information; +- Receiving topology updates from SDN controllers; +- Retrieval of logical network topologies that include combinations of logical and physical topologies. + +#### **11.5.2.2 Connection control function** + +Through a CPI, SDN controllers should support connection control functions including connection creation, connection modification, connection deletion, OAM configuration and activation and survivability mechanisms. + +#### **11.5.2.3 Instantiation/Deletion /Update of services** + +Controllers are responsible for computing a path for a connection request and providing the path to their client controllers or applications through a CPI, which should support: + +- Path computation of intra-domain, inter-domain or multi-layer for the transport network, according to the path constraint conditions in the connection request; +- Optimization of P2P paths, reconfiguring paths to achieve optimization; +- Requests for path (route) information needed to set up connections. + +#### **11.5.2.4 Resource virtualization/abstraction** + +A lower level controller can present its transport resource and virtual networks view to its client controllers and applications through the CPI. Client controller interaction over the CPI allows: + +- VN creation, modification and release request. +- Partition of network resources for different VNs according to policy. +- Providing different views (abstractions) of the resources, real and virtualized, under its control, subnetwork and link topological resource can be represented with varying degrees of detail (granularity). + +#### **11.5.2.5 Performance and fault management** + +Lower level controllers could provide performance and fault management related information to their clients through the CPI. Performance monitoring and fault detection are necessary for transport resources and virtual network resources. Dynamic service control policy enables the performance and fault management function. + +#### **11.5.2.6 Notifications and events** + +Notifications refer to the set of autonomous messages that provide information about events, for example, alarms, performance monitoring (PM) threshold crossings, object creation/deletion, attribute value change (AVC), state change, etc., related to resources in the controller's scope. These notifications may also include messages indicating service faults, performance degradation and so forth. + +Notifications are provided over the CPI by server controllers to their client. The mechanism used is a matter of implementation detail. + +#### **11.5.2.7 MC component information flows** + +Some of the information listed above that are supported over the CPI include the following MC component information flows: NCC-NCC and RC-RC. + +### 11.5.3 Interaction between NCCs over CPI + +In Figure 15-1, the NCC in the client controller sends the call request to the NCC in the server controller. The resource identifiers (i.e., SNP identifiers/name spaces) are sent from client NCC to server NCC. + +Through a CPI, a client NCC can initiate connection creation, connection modification, connection deletion and connection query requests. The interactions between NCCs over CPI are listed in this clause. + +#### 11.5.3.1 Call creation + +If the connection is setup is successful, the client NCC obtains connection identifiers and connections. + +The parameters sent from the client NCC to the server NCC over CPI could be: + +- SNP identifiers (or Name) in the client context; +- Direction of connection; +- Connection constraints including capacity, layer, latency, cost, etc. +- Required capacity. + +The resulting parameters returned from server NCC to client NCC over CPI could be: + +- Success/Failure; +- Connection identifiers in server context; +- Operational state; +- Connection details, see above parameters. + +#### 11.5.3.2 Call modification + +The parameters sent from the client NCC to the server NCC over CPI could be: + +- Connection identifiers in client context; +- Connection constraints including capacity, layer, latency, cost, etc. +- Required capacity. + +The resulting parameters returned from the server NCC to the client NCC over CPI could be: + +- Success/Failure; +- Operational state; + +#### 11.5.3.3 Call deletion + +The parameters sent from the client NCC to the server NCC over CPI could be: + +- Connection identifiers or name; + +The resulting parameters returned from the server NCC to the client NCC over CPI could be: + +- Identifiers of the deleted connection; +- State changes. + +#### 11.5.3.4 Call query + +The parameters sent from the client NCC to the server NCC over CPI could be: + +- Connection identifiers in client context; +- Connection constraints including capacity, layer, latency, cost, etc. + +The resulting parameters returned from the server NCC to the client NCC over CPI could be: + +- Connection identifiers in the server context; + +– Connection details. + +## 11.6 Control communications network + +The control communications network (CCN) that allows the MC components to exchange information is described in clause 11.6 of [ITU-T G.7701]. + +An MC function operates on resources using a resource view. This view is enabled by a name/address/identifier plan. For example, the [ITU-T G.7701] routing controller component views topology using the SNPP name space and the TAP component manages the mapping of the SNP name space to the FP name space (resource label). + +For the purposes of some MC functions, there does not have to be a distinction between VN and non-VN resource views. If the resource is a networking resource, path computation can operate on a combined topology without needing to know the difference. + +An SDN controller may have MC functions that have resources in scope whose FP name space is visible, as well as resources in scope whose FP name space is invisible. Note that the routing function only uses the SNP/SNPP name space, so it is not affected by FP name space's visibility. For discovery, TAP and LRM, the visibility of FP name space becomes important. + +MC functions in an SDN controller that configure FPs associated with transport network resources do so via the resource-control interfaces [ITU-T Y.3300] and the configuration and/or properties exposed are abstracted by means of information models (IMs) [ITU-T G.7711] and data models (e.g., Yang model). Specifically, the resource-control interface is the generic interface across which an instance of the SDN information model is managed. This interface provides high-level accesses to the network resources regardless of their respective technology. As the SDN architecture operates on an abstract model of the transport resources, there is no architectural distinction between the control of physical and virtual transport NEs. Each may have FP name spaces whose configuration enables transfer of information. + +# 12 Resilience + +Resilience for MC components is described in clause 12 of [ITU-T G.7701] + +# 13 Connection availability enhancement techniques + +Connection availability enhancement techniques are described in clause 13 of [ITU-T G.7701]. The role of the SDN RC, CC and NCC in connection availability enhancement is illustrated in Figure 13-1 of [ITU-T G.7701]. + +# 14 Topology and discovery + +In the logically centralized and hierarchical control mode of SDN, the topology of the transport network is maintained by the co-operation of multi-level controllers and their locally controlled transport network. + +Within one control domain, the transport network topology is auto-discovered by the discovery agent (DA) using the mechanisms described in [ITU-T G.7714] and [ITU-T G.7714.1]. The DA reports the discovery result to the SDN controller for that domain. + +When the control domain contains two inter-connected administrative domains, the links between them are often manually configured in the controller. In some scenarios, auto-discovery may be possible e.g., for an Ethernet link, link layer discovery protocol (LLDP) may be enabled to operate across the administrative boundary. + +The controller's view of its resources should be kept current since these may change over time due to failure, recovery, network build-out or administrative action. + +## 14.1 Creation of network topology by auto discovery procedure + +The auto discovery of links and neighbours happens in the transport network. Any in-band communications used for the auto discovery procedure defined in [ITU-T G.7714] and depicted in [ITU-T G.7701] happen across the layer adjacency between subnetworks under the control of the discovery agent (DA). The results (i.e., the observed adjacency to a specific far link endpoint, identified using transport forwarding end port (as defined in [ITU-T G.800]) identifiers) are reported to other components in the SDN controller (DA to TAP, then TAP to LRM which located in SDN controller). + +As shown in Figure 14-1 DA1 is responsible for the link end on subnetwork 1 and DA2 is responsible for the link end subnetwork 2. Through discovery messaging, DA1 and DA2 may discover the adjacency between the link ends. This and the capabilities of link are reported to the link end's TAP. The TAP maps the identifiers from the transport name space into the control name space used by the LRM and RC. This information contributes to the network topology graph created in the SDN controller. + + + +``` +graph TD; S1((Subnetwork 1)) --- S2((Subnetwork 2)); DA1[DA1] --> C[Controller]; DA2[DA2] --> C; C --> DA1; C --> DA2; DA1 --> S1; DA2 --> S2; +``` + +G.7702(22)\_F14-1 + +Diagram illustrating the auto discovery process between two subnetworks (Subnetwork 1 and Subnetwork 2) connected by a link. Both subnetworks have a Discovery Agent (DA1 and DA2 respectively) connected to a central Controller. Arrows indicate the flow of discovery messages from the DAs to the Controller and from the Controller to the DAs. + +**Figure 14-1 – Example of auto discovery between subnetworks** + +When multiple controllers are in use, the DAs need to determine which controller to notify about the link and its capability. Since a controller provides connection management across the link and needs to configure both ends of the link, the appropriate controller is the lowest level controller that has visibility to both ends of the link. If a DA does not have a direct association with the appropriate controller, the link discovery notification may be proxied by a lower level controller. + +## 14.2 Creation of abstracted network topology + +An abstracted network consists of subnetworks and links, which are created based on assignment of resources from the network topology known to the SDN controller, with consideration of policy, SLA, security, etc. The non-abstracted and abstracted subnetworks as well as links are equivalent with each other, aggregated or sliced from actual transport network resources or abstracted resources, as shown in Figure 14-2 as an example of discovery and creation of abstracted network. + + + +Diagram illustrating the discovery and creation of abstracted network topologies. At the top, Controller 3 is connected to two abstract topologies, 'Abstract topology A' and 'Abstract topology B', via 'Intra-domain' links. Below these, Controller 1 and Controller 2 are shown. Controller 1 is connected to DA1, which is connected to Domain 1. Controller 2 is connected to DA2, which is connected to Domain 2. Domain 1 and Domain 2 are connected to each other by a physical link. Arrows indicate the flow of information from the domains up through the DAs and controllers to the abstract topologies and finally to Controller 3. A small label 'G.7702(22)\_F14-2' is present at the bottom right of the diagram. + +**Figure 14-2 – Example of discovery and creation of abstracted network** + +In Figure 14-2 Controller 3 creates an abstracted network topology from network topologies 1 and 2. These topologies are auto discovered separately following the procedure described in clause 14.1. The DAs for network 1 notify Controller 1 of discovered links so it may assemble the topology of network 1 and the DAs in network 2 notify Controller 2 of the discovered links so it may assemble the topology of network 2. Based on the topology for network 1, Controller 1 creates the abstracted network A and reports it to Controller 3 by the CPI interface between Controller 1 and 3. + +The physical link between domain 1 and 2 can be configured manually or auto discovered by cooperation of the DAs for Domain 1 with Controller 1 as well as the DAs for Domain 2 with Controller 2. Thus controller 3's total network topology consists of abstract topology A, abstract topology B and the links between these two topologies. + +# 15 Controller interactions + +There are many possible combinations of controller interactions enabled by the architecture, particularly when considering the dimensions of single/multi resource layers and single/multi-level resource views. This clause describes component interactions for a controller that can configure the FP name space for resources. Other dimensions of recursion are then described including when the controller has only SNP/SNPP names spaces for its view of resources, when multiple server controllers are needed for a concatenated connection and when an interlayer call is needed. Once the recursive cases are described, combinations of them are understood to cover many possible arrangements. + +The semantics of multi-layer and multi-level are now described, followed by the types of controller interactions driven by the dimensions of recursion. + +The basic types of controller interactions are: + +- 1) Request to a controller where called MC components have FP name spaces in scope. The CC, TAP and DA components have interfaces to the resources and can configure forwarding. +- 2) Request to a controller where called MC components do not have FP name space in scope. Any connections computed with the SNP/SNPP name space require further resolution to FP name spaces. This triggers a recursive call to a server controller that supports the VN representation. +- 3) Request that triggers sequential (horizontal) calls culminating in a concatenation of subnetwork connections. Multiple server controllers are called to return subnetwork connections that are assembled in the calling controller. + +- 4) Interlayer request for connection that becomes a link in the VN of the client controller. The [ITU-T G.7701] NCC's "Client NCC coordination in" interface returns SNPs in the client context so adaptation is performed in the server controller. +- 5) Interlayer mapped server. A server controller with server layer resources sets up a connection that is presented as a pair of SNPs in the client controller. + +## 15.1 Interaction type 1 + +Since the controller involved in this type of interaction has the resource name space in scope and can configure forwarding no recursive calls follow from call/connection setup. + +### 15.1.1 Call and connection control + +The interaction of MC components within single layer network for call/connection control including NCC, DS, CC, RC, DA and LRM in a single level controller is illustrated in Figure 15-1. Here the TAP, DA and CC access the FP name space of the transport resources and can configure forwarding. + +**Call/Connection set-up process:** The calling/called party call controller (CCC) or NCC-1/NCC-2/NCC-3 with the client context sends the call request to the NCC with server context in controller n (# 1a, 1b and 1c). The NCC sends a client/server context mapping request to the Directory Services (DS) component (# 2) for identifier translation and mapping of virtual network name spaces. The NCC then transforms the call request (with all required information including SLA related performance) to a connection request to the CC (# 3) based on the Identifiers in the server context. The CC sends a route query to the RC (# 4) for a path. The RC computes a path to CC based on the topology and local connection status information which was provided by the LRM (# 5, # 6). Then CC sends the link connection request to LRM for transport network resource allocation (# 6). The LRM interacts with TAP (# 7) to configure the adaptation and termination functions that terminate a link. TAP has interfaces to resources (# 8) that use the FP name space, and these are not exposed SDN interfaces. This enables forwarding in the network resources. + + + +Diagram of call and connection control within single level control for single layer network. The diagram shows three resource groups (black, green, red) each containing an NCC (NCC-1, NCC-2, NCC-3) and a cloud representing a client context. These are connected to a central 'Controller n' which contains an NCC, DS, RC, CC, LRM, TAP, and DA. The NCC in Controller n is connected to the client contexts via interfaces 1a, 1b, and 1c. The NCC is also connected to the DS via interface 2, to the RC via interface 3, to the CC via interface 4, to the LRM via interface 5, to the TAP via interface 6, and to the DA via interface 7. The DA is connected to the Transport network via interface 8. The diagram is labeled G.7702(22)\_F15-1. + +**Figure 15-1 – Call and connection control within single level control for single layer network** + +**Connection status maintenance process:** When the connection status is affected by a defect in the transport resources that are in the scope of the controller, the LRM reports the local connection status to the CC and then to the NCC through the network connection status reporting interface. The NCC in the server controller queries the DS to obtain the mapping of the connection identifiers into the client contexts. The NCC in the server controller is responsible for sending the connection status update information to the NCCs in client controllers. If high level SDN controllers or external applications have subscribed to receive connection status information (#9), then this is provided by the notification component. + +### 15.1.2 Resource discovery, virtualization (name spaces and mappings) and resource view maintenance + +The interaction of MC components within single layer network for resource virtualization and resource view maintenance including NCC, DS, RC, LRM, TAP and DA in a single level controller is illustrated as in Figure 15-1. + +In Figure 15-1, the DA component is shown inside the boundary of an SDN controller. This indicates that the DA is one of MC components supporting the SDN controller. DA deployment is not required when physical network resources are manually configured. Therefore, the DA is an optional MC component of an SDN controller. Also, a DA may be deployed in a non-SDN environment. The DA is described in clause 8.3.5 of [ITU-T G.7701]. + +**Resource discovery process:** The LRM, TAP and DA interacts together to perform the resources discovery function. DAs at the end of a link discover the trail FP to FP resource information over that link through in-band communication. The relationship between two client FPs (cFPs) over the two server FPs (sFPs) can be inferred as defined in [ITU-T G.7714.1]. In general, multiple client FPs + +(cFPs) in different layers may be associated with one server FP (sFP) using the flexible adaptation function. The TAP is responsible for maintaining the relationship between the cFP and sFP, including the mapping of the namespace between SNPs and FPs. LRMs interact with TAPs and maintain the corresponding SNP to SNP relationship for links in the SNP name space. The LRM reports the local topology (nodes and links), resources and abilities information of transport network to the RC and constructs the underlying network topology and resource database. + +**Virtualization within a single level:** Virtualization can be performed within a single level based on the underlying network topology and resources database, which is maintained by the controller, to create/modify/delete VNs for a client. A controller has one RC instance for each client and server context. The RC in a server context maintains the resource information obtained from the LRMs, while the RC in a client context maintains the VN topology information for that client. The virtualization function in the controller maintains separate RC instances to construct the topology required by each client context. During this virtualization process, the RC may interact directly with the LRM to establish the availability of lower level resources and, if necessary, provide partial lower level resources to its client based on policy; or the RC may interact with CC and NCC to first establish a connection and then use this connection as the input to the RC in client context, then use it as a link. A separate name space mapping between the client context and the server context is required for each RC instance. + +#### **Resource view maintenance process:** + +In the initial state, a common pool of transport resources under the control of an administration are abstracted into virtual resources and then allocated to different clients, each with their own client context, for their dedicated usage. When a client context is deleted, the virtual network resources dedicated to that client should be deleted and the corresponding SNPs and FPs in the transport resources should be released. + +Once the topology and resources state change due to failure, recovery, network build-out or administrative action, the TAP will update the SNP name spaces and also the relationship between the cFP and sFP. The LRM will update the corresponding SNP to SNP relationship for links in the SNP name space and output the changes in local topology (nodes and links), resources and abilities information of transport network to the RC in the server context. With the support of DS to perform the virtualization function per client, the corresponding RC instance will input all the changed information to the RDB and notify the VN client of the virtual resource changes. + +## **15.2 Interaction type 2** + +Consider the controller n+1 in Figure 15-2 and a request to set up a connection within a local transport network 11. Controller n+1 views transport network 11 as a VN with an SNP/SNPP name space. It can compute a route in this name space but as its MC components do not have visibility of the FP name space it thus must request controller n' to make a connection. Controller n+1 would utilize its NCC, CC and RC, but not LRM and TAP as there is no visibility of the FP name space. The NCC in controller n' would return a pair of SNPs to the NCC in Controller n+1. + +This style of interaction drives recursion up/down a hierarchy of controllers. It covers the case where a client has a VN projected from a subset of resources and/or that is an abstraction of resources. After the controller processes the request, further requests to other controllers may be initiated (types 1,3,4 and 5). + +## **15.3 Interaction type 3** + +This interaction type drives horizontal recursion to perform concatenation of calls/connections between controllers. This style of interaction drives recursion across controllers. It covers the case where a client has a VN consisting of resources projected from multiple server controllers. + +Consider the controller n+1 in Figure 15-2 and a request to set up a connection from transport network 11 to transport network 12. + +### 15.3.1 Call and connection control + +A two level control hierarchy is given in Figure 15-2 as an example to illustrate an end to end call and connection control across two subnetworks and their interconnected links. The end to end connection is divided into three parts: the first part is within the scope of controller n'; the second is within scope of controller n''; the third is the inter-connection between network 11 and network 12, which is within the control scope of controller n+1. The interaction of MC components between the two levels and within each level are both illustrated and described below. + +**Connection set-up:** After the discovery and creation of abstracted network resource process for multiple domains in high level controller as described in clause 7.2.2, Controller n+1 found that the end to end connection set-up and release process need to be divided into three subnetwork connections, Controller n' is responsible for the connection set-up and release process within network 11, Controller n'' is responsible for the connection set-up and release process within network 12 and Controller n+1 is responsible for the inter-connection between network 11 and network 12. NCC in Controller n+1 separately sends the call request to the NCC-11 in Controller n' and the NCC-12 in Controller n''. Interworking between the two levels of controllers is performed via NCC to NCC interaction. Inside each controller, the internal procedure for call and connection configuration is performed as the same component interaction sequence (including NCC, DS, CC, RC and LRM) as described in clause 10.1.1. + + + +Figure 15-2: Connection set-up and release process for two level controllers. The diagram illustrates a three-tier control hierarchy. At the top, 'Controller n+1' contains components NCC, DS, RC, CC, LRM, and TAP. The NCC is connected to DS, RC, and CC. RC is connected to CC and LRM. LRM is connected to TAP. Below this, 'Controller n'' contains NCC-11, DS-11, RC-11, CC-11, LRM-11, and TAP-11, with similar internal connections. 'Controller n''' contains NCC-12, DS-12, RC-12, CC-12, LRM-12, and TAP-12, also with similar internal connections. Arrows show the flow of control: from Controller n+1's NCC to Controller n''s NCC-11 and Controller n'''s NCC-12. On the right, a 'Network resource view' shows three cloud-like shapes: 'Transport network-11', 'Transport network-12', and an unlabeled top cloud. Dashed lines connect the top cloud to both transport networks, and a solid line connects transport network-11 to transport network-12. Controller n+1's NCC is also connected to the top cloud. A small label 'G.7702(22)\_F15-2' is in the bottom right corner. + +Figure 15-2 – Connection set-up and release process for two level controllers + +**Connection status maintenance process:** The NCC-NCC instance is also involved in the connection status maintenance process. The LRM reports the local connection status to the CC and then to the + +NCC through the network connection status reporting interface. The NCC in the server controller is responsible for sending the connection status information to the NCCs in client controllers. + +## 15.4 Interaction type 4 + +Consider the controller 2 in Figure 15-3. It makes a request for a connection from its server controller 1. The RC in Controller 2 is aware of the adaptation potential of the link to the resource view of subnetwork C in Layer Y. The returned connection is in layer X and controller 2 views it as a link in layer X that becomes part of subnetwork B. The connection is able to use the new link in layer X. The Client NCC Coordination In interface of the [ITU-T G.7701] NCC is used. When the NCC in controller 1 receives the request, it proceeds with the same steps 2-8 as depicted in Figure 15-1. The reply to the NCC in Controller 2 over the Client NCC Coordination In interface provides a pair of SNPs in the calling layer (i.e., layer X). As described in [ITU-T G.7701], the configuration of adaptation between [ITU-T G.800] layers is performed in the server NCC which is the NCC in controller 1. + + + +Diagram illustrating the Client NCC Coordination In interface. Controller 2 (top) contains subnetworks B and C'. Controller 1 (bottom) contains subnetwork C. A vertical double-headed arrow labeled 'CPI' connects Controller 2 and Controller 1. To the right, a separate diagram shows Layer X containing subnetworks A and B, and Layer Y containing subnetwork C. A vertical line connects subnetwork B in Layer X to subnetwork C in Layer Y. The text 'G.7702(22)\_F15-3' is at the bottom right. + +**Figure 15-3 – Client NCC Coordination In interface** + +When controller 1 is processing the request, further recursive calls may be needed. For example, interaction types 2, 3 and 4. + +## 15.5 Interaction type 5 + +Consider the controller 2 in Figure 15-3. For a mapped server call, Controller 2 needs to have a multi-layer topology view. This can be accomplished by having a VN representation of subnetwork C which is from a different layer than subnetwork B. The multilayer topology is used by an RC in Controller 2, to calculate a route through both layer networks. The NCC-NCC call is made from Controller 2 to controller 1 using boundary resource identifiers in the context of subnetwork C. + +The returned SNPs are in layer X and controller 2 views it as the location of an adaptation into Layer Y. The connection in Layer X is able to use the connection that is created in layer Y. This is the mapped server case described in clause 7.8 of [ITU-T G.7701]. + +The same steps as described in clause 15.4 are performed when the NCC in Controller 1 receives the request however the SNPs returned are not added as a link to the topology in Controller 2. + +When controller 1 completes the request, further recursive NCC-NCC calls of interaction types 1 through 5 may be needed. + +# 16 Scalability considerations + +## 16.1 Scalability of the controller + +The controller can be scaled vertically and/or horizontally. + +Vertical scalability can be achieved using a hierarchical stack of controllers; using this recursive application of SDN controllers, the SDN control layer can be easily scaled to cover large networks. + +Recursion is illustrated in Figure 11-2. The number of layers employed depends on the size of the network. Increasing recursive depth is used for larger networks. + +Horizontal scalability can be achieved using multiple parallel SDN controllers (see SDN controller 1, SDN controller 2 and SDN controller n as shown in Figure 11-4). + +Furthermore, the scalability of a SDN controller can be extended by the implementation of controller stacking as long as the network performance is acceptable. + +## **16.2 Scalability of components** + +The scalability of a controller could be enhanced by implementing multiple instances of the same type of MC function and load balancing between those instances inside that controller. This approach is an implementation option of the architecture, other implementations are not excluded. + +# Annex A + +## Use of the CIM to represent resources + +(This annex forms an integral part of this Recommendation.) + +Information models provide management views of the resources that need to be controlled and managed. The relationship between both kinds of resources and instances of resources is specified by the information model. The transport network resource data stored in the databases of SDN controllers may be structured into data models (that are generated from information models). In a model-driven architecture CPIs are described by data models. For each client or server context, there is, conceptually, a (logical) database in which the data is structured into data models that are generated from the information model. These data models describe the information that is encoded in a protocol and passed over the CPI as shown in Figure A.1. It may be necessary to map between the representation in the SDN controller resource database and the information in the database of a client or server. For example, it may be necessary to map between the name space used by the SDN controller and the name space used in a server context or client context. Further, it may be necessary to map between the artifacts used in the SDN controller and the (possibly more abstract) artifacts used in the client context as described in clause 7.4. + + + +The diagram shows two SDN controllers connected by a dashed vertical line labeled 'CPI'. The top controller is represented by a black rectangle. Inside it, at the top, is a circular icon with a clockwise arrow. Below this is an orange rectangle labeled 'Server context'. Inside the 'Server context' rectangle is a purple rectangle labeled 'Logical database'. The 'Logical database' rectangle has small squares at its corners. The bottom controller is also represented by a black rectangle. Inside it, at the top, is a blue rectangle labeled 'Client context'. Inside the 'Client context' rectangle is a purple rectangle labeled 'Logical database'. The 'Logical database' rectangle has small squares at its corners. A dashed vertical line labeled 'CPI' connects the two controllers. An arrow points from the bottom of the top 'Logical database' to the top of the bottom 'Logical database'. + +Diagram illustrating the data model generated from CIM passed over CPI. It shows two controllers connected by a dashed line labeled CPI. The top controller contains a 'Server context' box with a 'Logical database' inside. The bottom controller contains a 'Client context' box with a 'Logical database' inside. An arrow points from the top logical database to the bottom logical database. + +G.7702(18)\_FA.1 + +**Figure A.1 – Data model generated from CIM passed over CPI** + +Further, if the network resource database in the SDN controller is constructed from the resource database in a number of server contexts it may be necessary to translate between the semantics of these databases. This semantic translation can be avoided if these resource databases are generated from a common information model e.g., ITU-T G.7711. + +For the case where network resources are managed by a SDN controller and legacy management systems (EMS/NMS) simultaneously, it is necessary to synchronize the network resource databases in the SDN controllers and EMS/NMS. Data synchronization can be implemented by data query or database synchronization. Data query is implemented by calling the data query interfaces inside the CPIs provided by MCS. Database synchronization is implemented by capturing the data changes of network resource databases and synchronising the changes between the databases of management/control systems according to the mapping relationship between the different information + +models of the network resources. Both methods require the mapping relationship between the different information models of the network resources. + +It should be noted that to fully map and interpret between two IMs, one IM has to be a super set of the other one. + +# Bibliography + +- [b-ITU-T G.872] Recommendation ITU-T G.872 (2019), *Architecture of the optical transport network*. +- [b-ITU-T G.7715] Recommendation ITU-T G.7715/Y.1706 (2002), *Architecture and requirements for routing in the automatically switched optical networks*. +- [b-ITU-T M.3400] Recommendation ITU-T M.3400 (2000), *TMN management functions*. +- [b-ONF TR-521] Open Networking Foundation (2016), *SDN Architecture 1.1, TR-521*. + + + + + +## 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.1-200303-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe93cd83519695f529933f288375c72d71b4e9af --- /dev/null +++ b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebf0a8ae94837636e32b982c492f437797bcbf53b8962fb8a0ed4268b2d3781f +size 32155 diff --git a/marked/G/T-REC-G.7713.1-200303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/G/T-REC-G.7713.1-200303-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.7713.1-200303-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa8dfa30c33d4530209c366d50e77da071751b22 --- /dev/null +++ b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75dccc3298d44161492481f2d85f9606c4ad0f23a2f848527d6842173990fda8 +size 38413 diff --git a/marked/G/T-REC-G.7713.1-200303-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e409918ccfffbb0eb81320ab10010106c2d5d6b3 --- /dev/null +++ b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0934942c90c0ff1407675160850eab26ef99c3249487bab0d4eb856e9694cb23 +size 11720 diff --git a/marked/G/T-REC-G.7713.1-200303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f71d1d0b01f98fd2ce93db1046f0f3667700a91 --- /dev/null +++ b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:719de5b5fff033f3ea1e880ab0c58aa65ae84cf116b479ef42eae4b489a2dbe1 +size 106899 diff --git a/marked/G/T-REC-G.7713.1-200303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..102d840449e63727309f431efa3cdb020aa8ce79 --- /dev/null +++ b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebde32df75d8b2e5fbea682047c55965d6c7cb91c826177010dcd37d26e70e1b +size 40863 diff --git a/marked/G/T-REC-G.7713.1-200303-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b782337163c756f291ec6f46160defdf5d72077 --- /dev/null +++ b/marked/G/T-REC-G.7713.1-200303-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14a4a4d51a07c996fd628734df47612f2c5ff905bc405d738b82ce66e51a9505 +size 45752 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38bdd7bc1d3581fbdc3cf6b035f618693dbe3846 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75efa8e3513a799767c04a0bb7bcd87a550f2378f5880629068581808c1c9f7f +size 7353 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..792b7e10208762a793beb9089373a72913543d70 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff2b0b53f440b870ea091e7318f8df425a825bf50c4b397ec7be5b9886e4f8a5 +size 70315 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/19f5ea8afbf380781eb0645831a88987_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/19f5ea8afbf380781eb0645831a88987_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..786b959c449f0010c3969f8b080c1ddda7b5b6d0 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/19f5ea8afbf380781eb0645831a88987_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33e9455c9c3dd991c585dfc05d3894b1d09cefc4c0951b48a2c1ec86b7f5fda8 +size 74639 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd5c54ebf124c9d6c39279f2d3e5d74077a3a0d6 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6573fe206753b07a2a747524ff13642880fadcb1c9faef9c55b6e910caf9bc0 +size 42869 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7235412156b34205092819f918065e939008c30f --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2b2d4dbacddd0081a39ffc91a1bc794c186bf8762c8f5c6f30b9d5d4f932819 +size 34672 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..044912621aa833d9326c21d8d7ed32e4fece6c36 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50f225ebd1b988b4ad6d406e7a3a7b8e0c1165af28b51fc7b88ab902062a418f +size 56856 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf28ecae9efb7f0465eda90da73b13026f0d7f4a --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2233c8ec09d8227df6c2ede1654e7482d092f8ccdd2061dcfca823609bf5526d +size 66048 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46b82a9bdc92db0a504d3d9181ea0e85ced3f743 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04c063ceaab1c62b113683daf6632505dd05b0f58b3d74fb6ace86b2d1120eac +size 60957 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1d6a4d44da50638f35b19ee933cc7d6b3ea3bac --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac95e66dd3477b8f2d19338c88e9f8a2a00ad84179c832490bd3c12a13d88973 +size 137807 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c527e4735b90f954fd0cf320c086ef4b29bb582 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18b9a5531ae573d586515061ed62c3910093c54513e94fddd95b441d44cb7ed8 +size 61769 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7d439df492140d75f8caeabb476fa8176dd91c7 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7923190a190e6bfff55d9f03b0ed411fa731bba5e2ebdd80befb3f2ae548605a +size 78622 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c55939e3dcc6394a7798cde00ec80e1432a2962 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dc8581197f7027debdaf03c1959a148c58fe93e20b575f5bd3beb81b4d429ee +size 37615 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecd50df9a9f09d212f0b2374b4258cb330d74bc6 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36e569dc55e7c7abe1a445668a50f9ebcec6f29dcd04efb64242ac2c8e3e1486 +size 50545 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b43f1e2ba73ceee9f7a0e811dd5d705b8e71101 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:080e43f55206976d78b998d50871f4eb10d5fb1a93020c135d7ca078d4fc6f43 +size 82195 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a7ef7307d9dc0a0ce1a43c18c42f4cac68ddb62 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e0466969b2b9af46779ef0194e28c6432f98781f6d9272164344cc41bea5249 +size 70184 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14a179ba98cd081bb517c82cc2bd43ab41ce2746 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:128f02ecd9138a3567326ee62827ffaa4eaf24863da53fbf1c639b3ccb42e8bb +size 71198 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de2473bd9fd154482c0db286924dc51004400306 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a16c4fe4c736f6f1e4bc9474da9b8897c3c6368de45d3ab6cfdb857194f765e3 +size 52204 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae0260a067c18d3d07ed3cf1fc4daf6c7cc7ad4e --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8052641221f2cf1d4921132baa2d811b61e0c602fd626771125d9ec0e7e0da0 +size 65964 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bdae5ed7ce4280ead50ba1fe9a6c9d77a6f36e2 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7359854cec51ec7cb790c956f0cdbc698c4d84b847c24d897c1d970ae4dc7aea +size 61961 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/ac31fdfebb9751f7f10416dfe33bc872_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/ac31fdfebb9751f7f10416dfe33bc872_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25fadf4c84269cd252a56b6ef3eb3b8a07085134 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/ac31fdfebb9751f7f10416dfe33bc872_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dce5fa4c9b4ad1af91d75b29c5870260c2a4918a13caa234854c45f6c4e0613 +size 54197 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d32fbdb58134628918836f1582e8ee65f6863580 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3d53ef6144f6e027300754feb1b3b28979c8dd0a7853e1d94c3db2bdaa07b6f +size 88540 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/c85b57b2414f341860dfc338e1cf2509_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/c85b57b2414f341860dfc338e1cf2509_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dedfc16be0846c6f7f14669c944e721a79e112de --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/c85b57b2414f341860dfc338e1cf2509_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca85a17257fd37ef6fb6bef0cbc120c16be7c6fbcd20563ba13430a67adf5023 +size 56847 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f847f59e606f7a199a1c9e1064f0d7166ab4bac --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff1282495251f8fcea7b1a6e6929927b2b2f95c8fbfed43b04150d5eef4184fc +size 126007 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77601243e41ea7f0dd9e66bb82914a5b360ea852 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67a62a7cfaf51a26c326b1d731f8add158fa1e86c28eb77e94dc59ce54a0674a +size 82513 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/d1c99a42332e5ee19f3b840281c26681_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/d1c99a42332e5ee19f3b840281c26681_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f7ca390ade241ffafd9bed19d62d0276b266b29 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/d1c99a42332e5ee19f3b840281c26681_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5da74acfc7877c64b0a881f01925ac072f996efcd63c3ceeb11535900efe934 +size 87127 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e674200ca9374a5c5da0c2a2950246b7242349f --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3997d8f12583d85c03d5280ff50393019413664ba1fe31c62484047bc5721f0e +size 127445 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.7721-202508-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ded1393c9d57a37fc2b9c161b44adb7b2784694 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb38627767b812cecb83934231d44dcf18a059f4e679e982ff637670d5bc1a83 +size 67134 diff --git a/marked/G/T-REC-G.7721-202508-I_PDF-E/raw.md b/marked/G/T-REC-G.7721-202508-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..08b96d06d6cfc17f7f16097cd313fce8ab135630 --- /dev/null +++ b/marked/G/T-REC-G.7721-202508-I_PDF-E/raw.md @@ -0,0 +1,1080 @@ + + +# Recommendation **ITU-T G.7721 (08/2025)** + +SERIES G: Transmission systems and media, digital systems and networks + +Data over Transport – Generic aspects – Transport network control aspects + +--- + +# **Management requirement and information model for synchronization** + + + +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 superimposed 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 | +| 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.* + +# Recommendation ITU-T G.7721 + +# Management requirement and information model for synchronization + +## Summary + +Recommendation ITU-T G.7721 provides the management requirements and a protocol-neutral management information model for managing network elements and network of synchronization, based on the synchronization architecture and equipment defined in ITU-T Recommendations. + +This Revision updates ITU-T G.7721 to align the information model for SyncPhy with the data set defined in Edition 5.2 of ITU-T G.781. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.7721 | 2018-11-29 | 15 | 11.1002/1000/13789 | +| 1.1 | ITU-T G.7721 (2018) Amd. 1 | 2022-11-13 | 15 | 11.1002/1000/15147 | +| 1.2 | ITU-T G.7721 (2018) Amd. 2 | 2024-12-07 | 15 | 11.1002/1000/16148 | +| 2.0 | ITU-T G.7721 | 2025-08-22 | 15 | 11.1002/1000/16397 | + +## Keywords + +Information model, management, protocol-neutral, synchronization, unified modelling language (UML). + +--- + +\* To access the Recommendation, type the URL
Fault Conditions | Prompt maintenance alarm indication (7) | Alarm indication to the remote equipment (3) | AIS sending (4) | Blocking of faulty speech channels | Pilot cut-off to the remote FDM terminal | +|---------------------|---------------------------------------------------------------------------------|-----------------------------------------|----------------------------------------------|----------------------------------------|----------------------------------------|------------------------------------------| +| PCM alarm | Loss of frame alignment and multiframe alignment or Loss of incoming signal (2) | Yes (8) | Yes | | Yes
(PCM → FDM) | | +| | Digital error ratio $10^{-4}$ or $10^{-3}$ (10) | Yes (8) | Yes | | | | +| | Reception of alarm indication from the remote equipment (2, 3) | Yes | | | | | +| | AIS receiving (4) | Yes | | | Yes
(PCM → FDM) | | +| FDM alarm | Absence of group pilot (5) | Yes | | Yes (9) | Yes | | +| | Pilot level deviation alarm (11) | Yes, if regulation is present | | | | | +| System alarm | Failure of power supply (2) | Yes | | | | Yes, depending on network applications | +| | System failure (6) | Yes | Yes, depending on network applications | Yes, depending on network applications | Yes, depending on network applications | Yes, depending on network applications | +| | Synchronisation failure | Yes | | | | | + +*Note 1* - A *Yes* in the table signifies that an action should be taken as a consequence of the relevant fault conditions. An open space in the table signifies that the relevant action should not be taken as a consequence of the relevant fault condition, if this 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. + +*Note 2* - The fault conditions "Loss of incoming signal", "Loss of frame alignment and multiframe alignment", "Reception of alarm indication to the remote equipment" and "Failure of power supply" are defined in Recommendation G.733. + +*Note 3* - For "Alarm indication to the remote equipment", data link bits are used. + +*Note 4* - The AIS can be used only in the new frame structure to be specified by Study Group XVIII. + +*Note 5* - The level, at which "Absence of group pilot" is detected, is under study. + +*Note 6* - The "System failure", which is only for the digital filtering transmultiplexer, corresponds to a fault detected by the transmultiplexer's supervision system, when it has one. + +*Note 7* - The consequent action "Prompt maintenance Alarm indication" and "Alarm indication to the remote equipment" are defined in Recommendation G.733. + +*Note 8* - When AIS is detected, the "Prompt maintenance alarm indication" associated with the "Loss of frame alignment and multiframe alignment" with the "Loss of incoming signal" or with the "Digital error ratio $10^{-4}$ " should be blocked. + +*Note 9* - The AIS is sent only if the 24 channels of a single PCM stream are in the alarm condition. + +*Note 10* - Depends on network applications. + +*Note 11* - "Pilot level deviation alarm" corresponds to a variation on the level of the incoming pilot from its nominal value by more than $\pm 4$ dB, as stated in CCITT Recommendation G.241, § 1. This applies only to transmultiplexers with automatic internal level regulation. \ No newline at end of file diff --git a/marked/G/T-REC-G.801-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.801-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..144b418da5e8721bdd37e20c7824b09bfa672e8d --- /dev/null +++ b/marked/G/T-REC-G.801-198811-I_PDF-E/raw.md @@ -0,0 +1,197 @@ + + + + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**G.801** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**DIGITAL NETWORKS** + +--- + +**DIGITAL TRANSMISSION MODELS** + +**ITU-T Recommendation G.801** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation G.801 was published in Fascicle III.5 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 TRANSMISSION MODELS** + +*(Malaga-Torremolinos, 1984)* + +The CCITT + +*considering* + +- (a) that digital networks support a wide variety of connections for which digital transmission impairments and other performance parameters need to be controlled; +- (b) that, if proper control is not exercised, then under certain circumstances, digital transmission impairments cause unacceptable service degradations; +- (c) that various network performance objectives need to be allocated to the elements of a digital network; +- (d) that equipment design objectives need to be formulated for individual digital elements; +- (e) that networks need to be configured to a level of transmission quality consistent with the needs of different services (voice and non-voice) and in particular of services in the ISDN; +- (f) that Administrations need to examine the effect on transmission quality of possible changes of impairment allocation in national networks; +- (g) that there is a need to test national rules for prima facie compliance with any impairment criteria which may be recommended by the CCITT for national and international systems, +- (h) that guidelines need to be formulated governing the use of certain digital elements (e.g. satellite links, transcoders, digital pads, circuit multiplication devices, etc.), + +*recommends* + +that in the study of digital transmission impairments and other performance parameters, the following network models and associated guidelines should be applied. + +## **1 Introduction** + +Digital transmission network models are hypothetical entities of a defined length and composition for use in the study of digital transmission impairments (e.g. bit errors, jitter and wander, transmission delay, availability, slip, etc.). The diversity of possible network situations requires that individual models can only represent a small portion of typical real entities. However, a limited number of such models (e.g. 2 or 3) together may be sufficiently representative to provide a useful tool upon which studies may be based. + +The network models, where applicable, take account of the following features: + +- a) physically reflect the length of the overall connection with some indication of frequency of occurrence, + +- b) identify boundaries between switching and transmission elements, +- c) give no indication of the means of implementing transmission between switching elements (e.g. metallic, optical, radio media, satellite etc.), +- d) describe in detail the user/network access arrangement in the local portion (i.e. customer to local exchange), +- e) take account of all possible usages or be independent of them, +- f) reflect the use of additional digital processing elements required in particular network configurations (e.g. $A-\mu$ converters, digital pads, transcoders, etc.). + +This Recommendation makes no statement in respect of the electrical and physical environment in which the network models operate. These aspects are currently the subject of study. In the application of these network models to the study of specific digital impairment (e.g. errors) arbitrary judgements may need to be made concerning the significance, in particular, of the electrical environment. + +## 2 Hypothetical reference connection (HRX) + +A digital HRX is a model in which studies relating to overall performance may be conducted, thereby facilitating the formulation of standards and objectives. In order to initiate studies directed at the performance of an ISDN, an all digital 64 kbit/s connection is considered. Since the overall network performance objectives for any performance parameter need to be consistent with user requirements, such objectives, in the main, should relate to a network model which is representative of the very long connection. The HRX shown in Figure 1/G.801 serves this purpose. It does not represent the rare worst case connection; although it does aim to encompass the vast majority of connections for each relation. Moreover, the difficulty of identifying every conceivable practical implementation of a connection and the undesirability of producing too many options naturally requires that this "standard HRX" may need to be appropriately modified in composition to suit the particular task in hand. A situation can be envisaged where many similar HRXs exist to serve specific functions, but in all cases they are derivatives of the "standard HRX". The potential proliferation of HRXs prevent their inclusion in this Recommendation. Any departure from the "standard HRX" may need to be shown in the Recommendation appropriate to that impairment or performance parameter. For example, see Recommendation G.821. They are not intended to be used for the design of transmission systems. + +The diversity in composition is particularly apparent when a distinction is made between average size and large countries and, therefore no one HRX can possibly accommodate such variations. In the process of apportionment the demarcation between national and international portions is unimportant as in most instances the intrinsic quality of circuit comprising both portions is the same. In contrast, however, the overall length is regarded as being critical and its choice is "country size" independent. Accordingly, the level of impairment actually experienced over a real connection is considered satisfactory if compatible with that stipulated for the longest HRX, taking due account of differences between the construction of the hypothetical and real connections. For a large proportion of real connections configured using equipment designs recommended by CCITT, the actual performance is likely to be significantly better. Those CCITT compliant connections which exceed the longest HRX in either length or complexity may not have controlled levels of performance; however, their impairment levels are unlikely to exceed those of the longest HRX by more than a factor of 2 and the design margins provided with individual items of equipment may well bring the impairment to within CCITT end-to-end performance specifications. + +In formulating the above HRX no account was taken of the following aspects: + +- maritime applications, +- semi-automatic connections (i.e. auto-manual), +- standby routing in case of failure. + +Two other HRXs have been included to facilitate studies over shorter connections with a view to establishing the typical performance levels likely to be achieved over frequently realized international circuits. These are given in Figures 2/G.801 and 3/G.801. + + + + + +Diagram of a standard digital hypothetical reference connection (moderate length) with a total length of 11 000 km. The connection is divided into three main segments: National (left), International (middle), and National (right). The left National segment is further divided into Local and National sub-segments. The sequence of components from left to right is: T-reference point, LE (Local Equipment), PC (Packet Controller), ISC (International Switching Centre), ISC, PC, LE, and CCITT - 67 201 T-reference point. The diagram shows a series of boxes representing these components, with some boxes containing an 'X'. + +Note – See Figure 1/G.801 for legend. + +FIGURE 2/G.801 + +### **Standard digital hypothetical reference connection (moderate length)** + + + +Diagram of a standard digital hypothetical reference connection (moderate length with subscriber situated near the International Switching Centre (ISC)) with a total length of 10 000 km. The connection is divided into three main segments: National (left), International (middle), and National (right). The left National segment is further divided into Local and National sub-segments. The sequence of components from left to right is: T-reference point, LE (Local Equipment), ISC (International Switching Centre), ISC, ISC, LE, and CCITT - 67 221 T-reference point. The diagram shows a series of boxes representing these components, with some boxes containing an 'X'. + +Note – See Figure 1/G.801 for legend. + +FIGURE 3/G.801 + +### **Standard digital hypothetical reference connection (moderate length with subscriber situated near the International Switching Centre (ISC))** + +## 3 Hypothetical reference digital link (HRDL) + +To facilitate the study of digital transmission impairments (e.g. bit errors, jitter and wander, slip, transmission delay) it is necessary to define network models comprising a combination of different types of transmission elements (e.g. transmission systems, multiplexers, demultiplexers, digital pads, transcoders). Such a model is defined as a Hypothetical Reference Digital Link (HRDL). The exact length and composition in respect of the number, type and disposition of equipments will depend on the digital impairment under study. For example, in the analysis of jitter accumulation in a network both transmission systems and multiplexers would need to be included to take account of the different jitter characteristics exhibited by such equipment types. In addition the HRDL can be regarded as a constituent element of an HRX thus permitting the apportionment of overall performance objectives to a shorter model. A length of 2500 km is considered as a suitable distance for a HRDL. + +The formulation of such models is the subject of further study. + +In CCIR Recommendations the term Hypothetical Reference Digital Path (HRDP) is sometimes used. This is equivalent to a Hypothetical Reference Digital Link (see Definition 3005 in Recommendation G.701). + +## 4 Hypothetical reference digital section (HRDS) + +To accommodate the performance specification of transmission systems (i.e. digital line and radio systems) it is necessary to introduce a Hypothetical Reference Digital Section (HRDS). Such a model is defined in Figure 4/G.801 for each level in the digital hierarchies defined in Recommendation G.702. The input and output ports are the recommended interfaces as given in Recommendation G.703 for hierarchical bit rates. The lengths have been chosen to be representative of digital sections likely to be encountered in real operational networks, and are sufficiently long to + +permit a realistic performance specification for digital radio systems. The model is homogeneous in that it does not include other digital equipments such as multiplexers/demultiplexers. This entity can form a constituent element of a HRDL. + + + +Diagram of a hypothetical reference digital section. It shows two rectangular blocks labeled 'Terminal equipment' connected by a horizontal line. The left input is labeled 'X kbit/s' and the right output is labeled 'X kbit/s'. Below the connection line is a double-headed arrow labeled 'Y km'. At the bottom right of the diagram is the text 'CCITT - 67 230'. + +*Note —* The appropriate value for “Y” is dependent on the network application. For now the lengths of 50 km and 280 km have been identified as being necessary (see Recommendation G.921). + +FIGURE 4/G.801 + +### **Hypothetical reference digital section** + +It is possible to relate the two following types of performance requirement to an HRDS: + +- the Network Performance Objectives (NPO) which are the objectives to be realized in a real network; +- the Equipment Design Objectives (EDO) which provide guidance to the designer of systems using specific transmission media and transmission techniques. + +*Note 1 —* The Equipment Design Objectives which normally appear in the appropriate transmission and switching system recommendations are formulated to ensure compatibility with the corresponding network performance objectives. + +*Note 2 —* An explanation of a Network Performance Objective and an Equipment Design Objective is given in Recommendation G.102. + +*Note 3 —* The formulation of a homogeneous entity of a realistic length permits specification and commissioning acceptance testing under real operational conditions. + +In a similar manner CCIR and CMTT have formulated media and application orientated models for use in their studies. The following recommendations describe the relevant models. + +- Recommendation 502-2 (Draft). Hypothetical Reference Circuit for Sound Programme Transmission. (Terrestrial systems and systems in the fixed-satellite service). +- Recommendation 521-1. Hypothetical Reference Digital Path for systems using digital transmission in the fixed-satellite service. +- Recommendation 556. Hypothetical Reference Digital Path for radio-relay systems for telephony. + +## ANNEX A + +(to Recommendation G.801) + +### **The application of Hypothetical Reference Models in the formulation of equipment design objectives** + +An important use of hypothetical reference models is to facilitate the apportionment of network performance + +objectives to constituent elements, prior to the derivation of equipment design objectives. To satisfactorily achieve this objective a diagrammatic representation of the approach adopted by CCITT in the formulation of equipment design objectives is shown in Figure A-1/G.801. + +The approach recognizes that it may be necessary to derive from the "standard HRX" a more appropriate HRX which better takes into account both the usage and the specific network performance parameter under study. The adoption of this approach will facilitate the formulation of rules governing the use of certain digital elements such as satellite links, transcoders, digital pads, etc. + +National Administrations are advised to develop their own representative network models reflecting the features of their evolving national digital network in order to validate prima facie compliance with international standards. + + + +``` + +graph TD + S1[Identify and specify a reference network model (i.e. "standard HRX") reflecting the evolving digital networks] --> S2[Identify transmission performance parameters and digital impairments that need to be controlled and specified] + S2 --> S3[Formulate an HRX (based on the "standard HRX") most appropriate to the network performance parameter or digital impairment under study] + S3 --> S4[Define end-to-end network performance criterion in relation to the most appropriate HRX taking into account what is achievable in terms of cost, what users require, subjective aspects, practical means of implementation, etc.] + S4 --> S5[Apportion network performance objective to individual digital elements using network models such as HRDL and HRDS] + S5 --> S6[Derive equipment design objectives from network performance objectives (the actual procedure will be dependent on the parameter under consideration)] + S6 --> S7[Formulate rules governing the use of certain digital elements (e.g. satellite links, echo suppressors, transcoders etc.)] + + subgraph Stages + direction LR + L1[Stage 1] --- S1 + L2[Stage 2] --- S2 + L3[Stage 3] --- S3 + L4[Stage 4] --- S4 + L5[Stage 5] --- S5 + L6[Stage 6] --- S6 + L7[Stage 7] --- S7 + end + +``` + +CCITT - 67240 + +Flowchart showing 7 stages for deriving equipment design objectives. Stage 1: Identify and specify a reference network model (i.e. 'standard HRX') reflecting the evolving digital networks. Stage 2: Identify transmission performance parameters and digital impairments that need to be controlled and specified. Stage 3: Formulate an HRX (based on the 'standard HRX') most appropriate to the network performance parameter or digital impairment under study. Stage 4: Define end-to-end network performance criterion in relation to the most appropriate HRX taking into account what is achievable in terms of cost, what users require, subjective aspects, practical means of implementation, etc. Stage 5: Apportion network performance objective to individual digital elements using network models such as HRDL and HRDS. Stage 6: Derive equipment design objectives from network performance objectives (the actual procedure will be dependent on the parameter under consideration). Stage 7: Formulate rules governing the use of certain digital elements (e.g. satellite links, echo suppressors, transcoders etc.). + +FIGURE A-1/G.801 + +The derivation of equipment design objectives +based on the use of network models \ No newline at end of file diff --git a/marked/G/T-REC-G.8011-202010-I_PDF-E/raw.md b/marked/G/T-REC-G.8011-202010-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..714ded4eec2b70483e48a3b69e8a3ff8373b5745 --- /dev/null +++ b/marked/G/T-REC-G.8011-202010-I_PDF-E/raw.md @@ -0,0 +1,574 @@ + + +**ITU-T** + +**G.8011/Y.1307** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(10/2020) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Packet over Transport aspects – Ethernet over Transport +aspects + +SERIES Y: GLOBAL INFORMATION +INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, +NEXT-GENERATION NETWORKS, INTERNET OF +THINGS AND SMART CITIES + +Internet protocol aspects – Transport + +# --- Ethernet service characteristics + +Recommendation ITU-T G.8011/Y.1307 + +# 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 | +| PACKET OVER TRANSPORT ASPECTS | G.8000–G.8999 | +| Ethernet over Transport aspects | G.8000–G.8099 | +| MPLS over Transport aspects | G.8100–G.8199 | +| Synchronization, quality and availability targets | G.8200–G.8299 | +| Mobile network transport aspects | G.8300–G.8399 | +| Service Management | G.8600–G.8699 | +| ACCESS NETWORKS | G.9000–G.9999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T G.8011/Y.1307 + +# Ethernet service characteristics + +## Summary + +Recommendation ITU-T G.8011/Y.1307 establishes a framework to describe network-oriented characteristics of Ethernet services based on the documents of a non-profit industry forum of network, cloud and technology providers, the MEF. The framework is supported by the modelling of Ethernet layer networks described by ITU-T and MEF. The service definition, service attributes and operation, administration and maintenance (OAM) introduced in this framework are used to create numerous specific Ethernet services. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|-----------------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.8011/Y.1307 | 2004-08-22 | 15 | 11.1002/1000/7358 | +| 1.1 | ITU-T G.8011/Y.1307 (2004) Cor. 1 | 2005-06-29 | 15 | 11.1002/1000/8530 | +| 1.2 | ITU-T G.8011/Y.1307 (2004) Amd. 1 | 2005-08-22 | 15 | 11.1002/1000/7359 | +| 2.0 | ITU-T G.8011/Y.1307 | 2009-01-13 | 15 | 11.1002/1000/9660 | +| 3.0 | ITU-T G.8011/Y.1307 | 2012-10-29 | 15 | 11.1002/1000/11782 | +| 3.1 | ITU-T G.8011/Y.1307 (2012) Cor. 1 | 2013-08-29 | 15 | 11.1002/1000/12002 | +| 4.0 | ITU-T G.8011/Y.1307 | 2015-01-13 | 15 | 11.1002/1000/12380 | +| 5.0 | ITU-T G.8011/Y.1307 | 2016-11-13 | 15 | 11.1002/1000/13093 | +| 6.0 | ITU-T G.8011/Y.1307 | 2018-11-29 | 15 | 11.1002/1000/13756 | +| 7.0 | ITU-T G.8011/Y.1307 | 2020-10-29 | 15 | 11.1002/1000/14504 | + +## Keywords + +Ethernet, Ethernet services layer connection, Ethernet service, framework, network-to-network interface, user-to-network interface. + +--- + +\* To access the Recommendation, type the URL
Remote defect indication (RDI),
Dual-ended proactive loss measurement (LM)
(fault 1 s, pm 100 ms, ps 3.33 ms) | MEPs | +| 3 | LBM | Loopback (unicast and multicast) message throughput | MEPs and MIPs
(connectivity verification) | +| 2 | LBR | Loopback (unicast and multicast) reply throughput | MEPs and MIPs
(connectivity verification) | +| 5 | LTM | Link trace message | MEPs and MIPs | +| 4 | LTR | Link trace reply | MEPs and MIPs | +| 6 | RFM | | | +| 7 | SFM | | | +| ITU-T SG15 defined | | | | +| 32 | GNM | Generic notification message | MEPs | +| 32-1 | BNM | Bandwidth notification message | MEPs | +| 33 | AIS | Alarm indication signal (AIS) | MEPs | +| 35 | LCK | Locked signal | MEPs | + +**Table 6-1 – Ethernet OAM PDU types and applications** + +| OpCode value | OAM PDU type | OAM application | OpCode relevance for MEPs/MIPs | +|-----------------------|--------------|---------------------------------------------|-------------------------------------| +| 37 | TST | Test, Throughput | MEPs | +| 39 | APS | Linear APS | Refer to [ITU-T G.8031] | +| 40 | APS | Ring APS | Refer to [ITU-T G.8032] | +| 41 | MCC | Maintenance communication channel | MEPs | +| 41-1 | EDM | Expected defect message | MEPs | +| 43 | LMM | Single-ended proactive and on-demand LM | MEPs | +| 42 | LMR | Single-ended proactive and on-demand LM | MEPs | +| 45 | IDM | Dual-ended delay and delay variation | MEPs | +| 47 | DMM | Single-ended delay and delay variation | MEPs | +| 46 | DMR | Throughput | MEPs | +| 49 | EXM | Experimental message | Outside the scope of [ITU-T G.8013] | +| 48 | EXR | Experimental reply | Outside the scope of [ITU-T G.8013] | +| 51 | VSM | Vendor-specific message | Outside the scope of [ITU-T G.8013] | +| 50 | VSR | Vendor-specific reply | Outside the scope of [ITU-T G.8013] | +| 52 | CSF | Client signal fail | MEPs | +| 53 | ISL | Dual-ended synthetic LM | MEPs | +| 55 | SLM | Single-ended synthetic LM | MEPs | +| 54 | SLR | Single-ended synthetic LM | MEPs | +| 34, 36, 38, 44, 60-63 | Reserved | | | +| MEF defined | | | | +| 56 | LLR | Latching loopback reply | | +| 57 | LLM | Latching loopback message | | +| 58 | SAT | Service activation test control protocol | | +| 59 | SAT | Service activation test control message | | +| IETF defined | | | | +| 64 | TRILL | Path trace reply | | +| 65 | TRILL | Path trace message | | +| 66 | TRILL | Multi-destination tree verification reply | | +| 67 | TRILL | Multi-destination tree verification message | | +| 68-59 | Reserved | | | + +NOTE 1 – The CCM PDU supports multiple applications, namely continuity check (CC), remote defect indication (RDI) and loss measurement (LM), and each application requires a different message rate (default rate for fault is 1 second, pm 100 msec, APS 3.33 msec.) + +NOTE 2 – There has been agreement among IEEE 802.1, MEF, and ITU-T SG15 that the assignee SDOs will also be responsible for the YANG model of their respective OAM. In ITU-T, the ET OAM (i.e., Carrier-grade Ethernet OAM) is specified in [ITU-T G.8013] with the equipment functional model in [ITU-T G.8021], the management requirements in [ITU-T G.8051] and information model in [ITU-T G.8052]. + +NOTE 3 – For some OAM PDUs, such as CCM and LBM/LBR, while the basic PDUs are defined in [IEEE 802.1Q], some of their usages are further enhanced in [ITU-T G.8013] and [ITU-T G.8021] to provide specific OAM application needs. For example, the LBM/LBR PDUs are used to provide the following OAM functionalities: + +- LB\_Discover: to discover the MAC addresses of the other MEPs in the same MEG. +- LB\_Series: to send a series of N LB messages to a particular MEP/MIP and report back the total number of received LBR frames, as well as counts of specific errors. +- LB\_Test: to send a series of LB messages carrying a test pattern to a particular MEP; and report back the total number of LBM frames sent, as well as the total number of LBR frames received. + +The UML model of these OAM applications is defined in [ITU-T G.8052] and the corresponding pruned/refactored UML and YANG are defined in this Recommendation. The YANG model of this Recommendation augments the IEEE 802.1Q base YANG model. + +NOTE 4 – OAM messages (requests and responses) are configured and processed at the MEP/MIP. Thus, consistent model/view among the SDOs on MEP/MIP is critical, regardless of whether they have formal UML MEP/MIP model (such as ITU-T SG15 in [ITU-T G.8052]) or not (such as [IEEE 802.1Q]). The base YANG model of MEP/MIP for connectivity fault management (CFM) is defined in [IEEE 802.1Q]. It is used as the base for augmentation for the YANG model of this Recommendation. + +The ET OAM functions covered in this Recommendation complements the [IEEE 802.1Q] defined CFM functions. + +The UML information model for the ET OAM is defined in clause 7. + +The YANG module for the ET OAM is contained in clause 8.1. This YANG module is translated from the ET OAM UML information model and augments the IEEE 802.1Q CFM YANG module `ieee802-dot1q-cfm.yang`. + +To ensure the seamless augmentation of the ET OAM YANG to the IEEE 802.1Q CFM YANG, the CFM YANG has been reverse-engineered into UML form to assist the modelling (pruning and refactoring of the base ITU-T G.8052 UML model). The reverse-engineered UML is contained in clause 7.1. + +# 7 Ethernet transport OAM information model + +## 7.1 IEEE CFM UML model reverse-engineered from the CFM YANG + +To assist ET OAM UML pruning and refactoring and to ensure that the translated ET OAM YANG can seamlessly augment the IEEE 802.1Q CFM YANG, the CFM YANG modules have been manually reverse-engineered into UML form. The model files of the CFM UML model are provided in clause 7.3. + +Contained in Annex A are the UML diagrams extracted from the CFM UML model. Contained in Appendix I are the IEEE 802.1Q CFM YANG modules. + +## 7.2 Overview of the ET OAM model + +This clause specifies the UML information model of the ET OAM functions identified in clause 6. This information model is derived through pruning and refactoring the ITU-T G.7711 core information model and ITU-T G.8052 foundation ET NE information model. + +### 7.2.1 ITU-T G.8052 base object classes + +To manage the ET OAM functions identified in clause 6, the following [ITU-T G.8052] object classes are considered for pruning/refactoring to meet the needs of this Recommendation: + +- ETH\_TrailTerminationPoint/Bidirectional/Sink/Source *and the subordinate Pacs* +- ETH\_ConnectionTerminationPoint/Bidirectional/Sink/Source *and the subordinate Pacs* +- Mep/ Bidirectional/Sink/Source +- MipBidirectional +- MepControl +- MipControl +- MeasurementJobControl +- OnDemandMeasurementJob +- OnDemandMeasurementJobControl +- OnDemandDualEndedMeasurmentJobControlSink +- OnDemandDualEndedMeasurmentJobControlSource +- OnDemandSingleEndedMeasurementJobControl +- ProActiveMeasurementJobControl +- ProActiveDualEndedMeasurementJobControlSink +- ProActiveDualEndedMeasurementJobControlSource +- ProActiveSingleEndedMeasurementJobControl +- CurrentData/HistoryData +- ProactiveDmCurrent/HistoryData +- ProactiveLmCurrentData/HistoryData +- Proactive1SlCurrentData/HistoryData +- Proactive1DmCurrentData/HistoryData +- ThresholdProfile + +Besides the above identified [ITU-T G.8052] object classes, additional object classes and interface classes are defined in this Recommendation specifically for augmenting the IEEE 802.1Q CFM base model. + +The object classes and interface classes of the UML model of this Recommendation are organized in three modules as follows. + +- The itut-eth-oam-bridge module + - This module consists of object classes for binding the forwarding plane with the MEP and MIP in the case IEEE 802.1Q bridges are deployed in the forwarding plane. + - It consists of the following three object classes: + - *MepBridgePortSpec*: It references the bridge port and augments the MEP + - *MipBridgePortSpec*: It references the bridge port and augments the MIP + - *MgBridgeSpec*: It augments the maintenance group (MG) + - See Figures 7-1 and 7-3 for additional information. +- The itut-eth-oam-am module + - This module consists of object classes for alarm management. It allows decoupling implementation of alarm management from performance monitoring and maintenance. + - It consists of the following object classes: + +- EthAmSpec: It augments the MEP for alarm severity assignments +- AlarmSeverityAssignmentProfile: It specifies the alarm severity assignments. +- Note that alarm management information model is deemed not mature yet and the classes are marked as experimental in the model, and therefore they are not translated into YANG and are not included in the YANG data model provided in clause 8.1. +- The itut-eth-oam module + - This module consists of object classes and interface classes for ET OAM performance monitoring, including pro-active monitoring and on-demand monitoring, and maintenance operations. + - It has the following performance measurement related object classes:1 + - EthMepOamSpec + - EthMeaJobPac + - ProActiveDualEndedMeaJob + - ProActiveDualEndedMeaJobControlTarget + - DualEndedCurrentData + - DualEndedHistoryData + - ProActiveDualEndedMeaJobControlInitiator + - ProActiveSingleEndedMeaJob + - ProActiveSingleEndedMeaJobControl + - SingleEndedCurrentData + - SingleEndedHistoryData + - OnDemandDualEndedMeaJob + - OnDemandDualEndedMeaJobControlTarget + - OnDemandDualEndedMeaJobControlInitiator + - OnDemandSingleEndedMeaJob + - OnDemandSingleEndedMeaJobControl + - ThresholdProfile + - It has the following maintenance operation related classes: + - EthMepOamSpec, which has the following attributes for loopback and link trace states + - loopbackSeriesState + - loopbackDiscoveryState + - linkTraceState + - LoopbackInputOamSpec datatype, which augments the IEEE CFM LoopbackInputGrouping datatype + - LinktraceInputOamSpec datatype, which augments the IEEE CFM LinktraceInputGrouping datatype + - LinktraceResponseOamSpec datatype, which augments the IEEE CFM Response datatype + +### 7.2.2 Augmentation to the IEEE CFM reverse-engineered UML + +The YANG model described in this Recommendation aims to augment the IEEE 802.1Q CFM YANG for the ETH OAM functionality. In UML form, the ITU-T G.8052.1 UML model aims to augment the IEEE 802.1Q CFM UML. + +--- + +1 Indentation in the listing reflects subordination hierarchy. + +Figure 7-1 provides an overview of the augmentation relationship between the IEEE 802.1Q classes and those defined in this Recommendation. It illustrates, at high level, that: + +- EthMepOamSpec augments IEEE Mep for the ETH OAM (see Figure 7-4 for details) +- EthMgOamSpec augments IEEE MaintenanceGroup for the ETH MIP (see Figure 7-10) +- MepBridgePortSpec augments IEEE Mep and also references IEEE BridgePort to associate the MEP (that supports the ITU-T ETH OAM functionalities) with the bridge port (see Figure 7-3) +- MipBridgePortSpec augments ITU-T Mip and also references IEEE BridgePort to associate the MIP (that supports the ITU-T ETH OAM functionalities) with the bridge port (see Figure 7-3) +- MgBridgeSpec augments IEEE MaintenanceGroup for ITU-T OAM fault management support (see Figure 7-3) + + + +``` + +classDiagram + class MgBridgeSpec { + <
NameType | «Enumeration»
PcpSelectionType | «DataType»
PortNumberType | «DataType»
PriorityType | «DataType»
TrafficClassType | «DataType»
VidRangeType | «DataType»
VlanId | «DataType»
VlanIndexType | +| nameType: String [1] | P0D
P1D
P2D
P3D | portNumberType: Integer [1] | priorityType: Integer [1] | trafficClassType: Integer [1] | vidRangeType: String [1] | vlanId: Integer [1] | vlanIndexType: Integer [1] | + +UML Class Diagram for IEEE 802.1Q model. It shows several classes and their relationships. PortMapGrouping is associated with PortMap (1 to +). PcpDecodingTableGrouping is associated with PcpDecodingMap (1 to +). PcpEncodingTableGrouping is associated with PcpEncodingMap (1 to +). TrafficClassTableGrouping is associated with TrafficClassMap (1 to +). PcpDecodingMap is associated with DecodingPriorityMap (1 to +). PcpEncodingMap is associated with EncodingPriorityMap (1 to +). TrafficClassMap is associated with AvailableTrafficClass (1 to +). PriorityRegenerationTableGrouping and ServiceAccessPriorityTableGrouping are shown as tables with priority values. BridgePortStatisticsGrouping is shown as a table with various counters. + +Figure A.8 – IEEE 802.1Q model – Data types + + + +**«Enumeration» ChassisIdSubtypeType** + +| | +|-------------------| +| chassis-component | +| interface-alias | +| port-component | +| mac-address | +| network-address | +| interface-name | +| local | + +**«DataType» ChassisIdType** + +| | +|-----------------------| +| chassisId: String [1] | +|-----------------------| + +**«Enumeration» PortIdSubtypeType** + +| | +|------------------| +| interface-alias | +| port-component | +| mac-address | +| network-address | +| interface-name | +| agent-circuit-id | +| local | + +**«DataType» PortIdType** + +| | +|--------------------| +| portId: String [1] | +|--------------------| + +UML Class Diagram for IEEE 802.1AB Data types. It shows four classes: ChassisIdSubtypeType (Enumeration), ChassisIdType (DataType), PortIdSubtypeType (Enumeration), and PortIdType (DataType). + +Figure A.9 – IEEE 802.1AB Data types + + + +**«Enumeration» ChassisIdSubtypeType** + +| | +|-------------------| +| chassis-component | +| interface-alias | +| port-component | +| mac-address | +| network-address | +| interface-name | +| local | + +**«DataType» ChassisIdType** + +| | +|-----------------------| +| chassisId: String [1] | +|-----------------------| + +**«DataType» MacAddress** + +| | +|------------------------| +| macAddress: String [1] | +|------------------------| + +**«Enumeration» PortIdSubtypeType** + +| | +|------------------| +| interface-alias | +| port-component | +| mac-address | +| network-address | +| interface-name | +| agent-circuit-id | +| local | + +**«DataType» PortIdType** + +| | +|--------------------| +| portId: String [1] | +|--------------------| + +**«DataType» VlanId** + +| | +|-------------------------| +| vlanId:
Note: there is no ccm priority in IEEE::MaintenanceAssociation, although there is IEEE::Mep::ccmLtmPriority | +| Mep::lckPeriod | refactored | Moved to (refactored into) datatype EthAisLckCommon | +| Mep::lckPriority | refactored | Moved to (refactored into) datatype EthAisLckCommon | +| MEP Sink | | | +| MepSink::peerMepRefList | pruned | Note: Seems indirectly from Mep through the association to MaintenanceAssociationMepList to the peer Mep; but the cardinality is only 1 | + +**Table II.1 – Ethernet MEP classes pruning/refactoring** + +| Source artefact | pruning/refactoring | Rationale | +|-------------------------------------------------------------|---------------------------------|-------------------------------------------------------------------------------------------------------------| +| MepSink::aisPeriod | refactored | Moved to (refactored into) datatype EthAisLckCommon | +| MepSink::aisPriority | refactored | Moved to (refactored into) datatype EthAisLckCommon | +| MepSink::isCsfReported | refactored | Moved to (refactored into) datatype EthCsf | +| MepSink::isCsfRdiFdiEnabled | refactored | Moved to (refactored into) to datatype EthCsf::csfConfig | +| MepSink::currentProblemList | To be refactored | To be modelled in the Alarm model of [ITU-T G.8052.1] | +| MepSink::bandwidthReport | refactored | Moved to (refactored into) datatype EthBandwidthNotification | +| MepSink::lDmPriority | refactored | Moved to (refactored into) datatype OamDmConfig | +| MepSink::_onDemandDualEndedMeasurementJobControlSink | refactored | OnDemandDualEndedMeaJobControlTarget | +| MepSink::_proactiveDualEndedMeasurementJobControlSink | refactored | ProActiveDualEndedMeaJobControlTarget | +| MEP Source | | | +| MepSource::mepIdentifier | pruned | Available in IEEE::Mep::_mepId | +| MepSource::csfConfig | refactored | Moved to (refactored into) datatype EthCsf | +| MepSource::csfPeriod | refactored | Moved to (refactored into) datatype EthCsf | +| MepSource::csfPriority | refactored | Moved to (refactored into) datatype EthCsf | +| MepSource::apsPriority | refactored | Moved to (refactored into) datatype EthAps | +| MepSource::_proactiveDualEndedMeasurementJobControlSource | refactored | ProActiveDualEndedMeaJobControlInitiator | +| MepSource::_onDemandMeasurementJobControlSource | refactored | OnDemandDualEndedMeaJobControlInitiator | +| MEP Bidirectional | | | +| MepBidirectional::_associatedRapsGroupRef | pruned | Ring protection modelling is not supported by the current version of [ITU-T G.8052.1] and [ITU-T G.8052.2]. | +| MepBidirectional::_associatedSncpGroupRef | refactored in [ITU-T G.8052.2.] | In [ITU-T G.8052.2], the Sncp model has referenced to the MEP object. | +| MepBidirectional::_onDemandSingleEndedMeasurementJobControl | refactored | OnDemandSingleEndedMeaJobControl | + +**Table II.1 – Ethernet MEP classes pruning/refactoring** + +| Source artefact | pruning/refactoring | Rationale | +|--------------------------------------------------------------|---------------------|-----------------------------------| +| MepBidirectional::_proactiveSingleEndedMeasurementJobControl | refactored | ProActiveSingleEndedMeaJobControl | + +**Table II.2 – Ethernet MIP classes pruning/refactoring** + +| Source artefact | pruning/refactoring | Rationale | +|-----------------------------------------------|---------------------|---------------------------------------------------------------------------------------------------------------| +| MIP Bidirectional | | | +| MipBidirectional::mipMac | retained | Not in IEEE::Mip.
Moved (re-factored) to Mip::mipMac | +| MipBidirectional::mel | pruned | The IEEE MIP has attribute mdLevel. An ITU-T MEG is equivalent to an IEEE MD which contains only one IEEE MA. | +| MipBidirectional::isFullMip | retained | Not in IEEE::Mip.
Moved (re-factored) to Mip::isFullMip | +| G8052LocalClass::localId | retained | Not in IEEE::Mip.
Moved (re-factored) to Mip::name | +| Raps Capable Half MIP Bidirectional | | | +| RapsCapableHalfMipBidirectional::mipMac | pruned | Ring protection modelling is not supported by the current version of ITU-T G.8052.1 and [ITU-T G.8052.2]. | +| RapsCapableHalfMipBidirectional::mel | pruned | Ring protection modelling is not supported by the current version of ITU-T G.8052.1 and [ITU-T G.8052.2]. | +| RapsCapableHalfMipBidirectional::rapsPriority | pruned | Ring protection modelling is not supported by the current version of ITU-T G.8052.1 and [ITU-T G.8052.2]. | +| G8052LocalClass::localId | pruned | Ring protection modelling is not supported by the current version of ITU-T G.8052.1 and [ITU-T G.8052.2]. | + +**Table II.3 – Ethernet operations pruning/refactoring** + +| Source artefact | pruning/refactoring | Rationale | +|-----------------|---------------------|-----------| +| EthMepInterface | | | + +**Table II.3 – Ethernet operations pruning/refactoring** + +| Source artefact | pruning/refactoring | Rationale | +|-------------------------------------------------------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| mepBi_establishOnDemandSingleEndedMeasurementJob | pruned | Achieved via object creation of an instance of OnDemandSingleEndedMeaJob and a subtending OnDemandSingleEndedMeasurementJobControl instance | +| mepBi_establishProActiveSingleEndedMeasurementJob | pruned | Achieved via object creation of an instance of ProActiveSingleEndedMeasurementJob and a subtending ProActiveSingleEndedMeasurementJobControl instance | +| mepSi_establishOnDemandDualEndedMeasurementJobSink | pruned | Achieved via object creation of an instance of OnDemandDualEndedMeasurementJob and a subtending OnDemandDualEndedMeasurementJobControlTarget instance | +| mepSi_establishProActiveDualEndedMeasurementJobSink | pruned | Achieved via object creation of an instance of ProActiveDualEndedMeasurementJob and a subtending ProActiveDualEndedMeasurementJobControlTarget instance | +| mepSi_getSvdCcm | To be modelled | No equivalence in IEEE CFM | +| mepSi_testResponderStart | refactored | No equivalence in IEEE CFM. TST is ITU-T OAM
Modelled as OnDemandDualEndedMeaJob with DualEndedOamType being TST. | +| mepSi_testResponderTerminate | refactored | No equivalence in IEEE CFM. TST is ITU-T OAM
Modelled as OnDemandDualEndedMeaJob with DualEndedOamType being TST. | +| mepSo_establishOnDemandDualEndedMeasurementJobSource | refactored | Achieved via object creation of an instance of OnDemandDualEndedMeasurementJob and a subtending OnDemandDualEndedMeasurementJobControlInitiator instance | +| mepSo_establishProActiveDualEndedMeasurementJobSource | refactored | Achieved via object creation of an instance of ProActiveDualEndedMeasurementJob and a subtending | + +**Table II.3 – Ethernet operations pruning/refactoring** + +| Source artefact | pruning/refactoring | Rationale | +|-----------------------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | ProActiveDualEndedMeasurementJobControlInitiator instance | +| mepSo_linkTrace | augment | Augment the IEEE CFM model:
– augment IEEE CFM Mep with EthMepOamSpec::linkTraceState
– augment IEEE CFM Responses with LinktraceResponseOamSpec
– augment IEEE CFM LinktraceInputGrouping with LinktraceInputOamSpec | +| mepSo_loopbackDiscover | augment | No equivalence in IEEE CFM. LB Discover is ITU-T OAM
Augment the IEEE CFM model:
– augment IEEE CFM Mep with EthMepOamSpec::loopbackDiscoveryState
– augment IEEE CFM LoopbackInputGrouping with LoopbackInputOamSpec | +| mepSo_loopbackSeries | refactored | No equivalence in IEEE CFM. LB Series is ITU-T OAM
Augment the IEEE CFM model:
– augment IEEE CFM Mep with EthMepOamSpec::loopbackSeriesState
– augment IEEE CFM LoopbackInputGrouping with LoopbackInputOamSpec | +| mepSo_loopbackTest | refactored | No equivalence in IEEE CFM. LB Test is ITU-T OAM
Modelled as OnDemandSingleEndedMeaJob with SingleEndedOamType being TST_LMB. | +| mepSo_loopbackTestTerminate | refactored | No equivalence in IEEE CFM. LB Test is ITU-T OAM
Modelled as OnDemandSingleEndedMeaJob with SingleEndedOamType being TST_LMB. | +| mepSo_testInitiatorStart | refactored | No equivalence in IEEE CFM. TST is ITU-T OAM
Modelled as OnDemandDualEndedMeaJob | + +**Table II.3 – Ethernet operations pruning/refactoring** + +| Source artefact | pruning/refactoring | Rationale | +|------------------------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | with DualEndedOamType being TST. | +| mepSo_testInitiatorTerminate | refactored | No equivalence in IEEE CFM. TST is ITU-T OAM
Modelled as OnDemandDualEndedMeaJob with DualEndedOamType being TST. | +| mepControl_createMep | pruned | Achieved via object creation of an instance of Mep | +| mepControl_deleteMep | pruned | Achieved via object deletion of an instance of Mep | +| mepControl_getAllContainedMeps | pruned | Achieved via retrieval of all object instances of Mep | +| mepControl_modifyMep | pruned | Achieved via object modification of an instance of Mep | +| meaJobControl_abortOnDemandMeasurementJob | refactored | Achieved via object deletion of the OnDemandMeasurementJob | +| meaJobControl_disableProActiveMeasurementJob | refactored | No equivalence in IEEE CFM. Measurement is ITU-T OAM
Modelled with ProActiveSingleEndedMeaJobControl::enabled, ProActiveDualEndedMeaJobControlTarget::enabled, and ProActiveDualEndedMeaJobControlInitiator::enabled | +| meaJobControl_enableProActiveMeasurementJob | refactored | No equivalence in IEEE CFM. Measurement is ITU-T OAM
Modelled with ProActiveSingleEndedMeaJobControl::enabled, ProActiveDualEndedMeaJobControlTarget::enabled, and ProActiveDualEndedMeaJobControlInitiator::enabled | +| meaJobControl_getAllContainedMeasurementJobs | refactored | Achieved via retrieval of all contained measurement job object instances | +| meaJobControl_getCurrentDataValues | refactored | Achieved via retrieval of CurrentData object instances. | +| meaJobControl_getHistoryDataValues | refactored | Achieved via retrieval of HistoryData object instances. | +| meaJobControl_terminateProActiveMeasurementJob | refactored | No equivalence in IEEE CFM. Measurement is ITU-T OAM | + +**Table II.3 – Ethernet operations pruning/refactoring** + +| Source artefact | pruning/refactoring | Rationale | +|--------------------------------------------------------|---------------------|--------------------------------------------------------------------------------------------------------------------| +| | | Achieved via deletion of ProActiveMeasurementJob | +| onDemandSingleEndedMeaJobControl_getIntermediateReport | refactored | No equivalence in IEEE CFM. Measurement is ITU-T OAM
Achieved via interface OdSeMjAction::getIntermediateReport | +| onDemandDualEndedMeaJobControlSi_getIntermediateReport | refactored | No equivalence in IEEE CFM. Measurement is ITU-T OAM
Achieved via operation OdDeMjAction::getIntermediateReport | +| EthMipInterface | | | +| mipControl_createMip | pruned | Achieved via object creation of an instance of Mip | +| mipControl_createRapsCapableMip | pruned | Ring protection modelling is not supported by the current version of ITU-T G.8052.1 and [ITU-T G.8052.2]. | +| mipControl_deleteMip | pruned | Achieved via object deletion of an instance of Mip | +| mipControl_getAllContainedMips | pruned | Achieved via retrieval of all contained instances of Mip | + +## Appendix III + +## Client and server implementation compatibility + +(This appendix does not form an integral part of this Recommendation.) + +Client and server implementation scenarios. + +| | IEEE client
ieee yang | ITU client
ieee yang + itu yang | IEEE + ITU client
ieee yang + itu yang | +|--------------------------------------------------------|-------------------------------------------------|-------------------------------------------|-------------------------------------------| +| IEEE server
ieee yang | A
ieee yang | D (Note 3)
ieee yang | G (Note 5)
ieee yang | +| ITU server
ieee yang + itu yang +
deviation yang | B (Note 1)
ieee yang + deviation yang | E (Note 4)
ieee yang + itu yang | H (Note 6)
ieee yang + itu yang | +| IEEE + ITU server
ieee yang + itu yang | C (Note 2)
ieee yang | F (Note 4)
ieee yang + itu yang | I (Note 7)
ieee yang + itu yang | + +NOTE 1 – The IEEE client will only configure the ieee yang, taking into account the deviations provided by the server, and ignore the itu yang modules + +NOTE 2 – The IEEE client will only configure the ieee yang and ignore the itu yang modules + +NOTE 3 – The ITU client understands that the server cannot support ITU-T features, and it will only configure the subset of the ieee yang which are in common between [IEEE 802.1Q] and [ITU-T G.8021] + +NOTE 4 – The ITU client will configure the itu yang and only the subset of the ieee yang which is needed to support the features defined by [ITU-T G.8021] + +NOTE 5 – The IEEE + ITU client understands that the server is IEEE and it will only configure the ieee yang + +NOTE 6 – The IEEE + ITU client understands that the server is ITU and it will configure the itu yang and only the subset of the ieee yang which is needed to support the features defined by [ITU-T G.8021] + +NOTE 7 – The IEEE + ITU client will configure both the ieee yang and the itu yang + +In scenarios B, E and H, YANG deviation statements are used by the ITU server to inform the client which part of the IEEE CFM YANG model have not been implemented because required by [IEEE 802.1Q] but not required by [ITU-T G.8021]. + +Clause 7.20.3 of [IETF RFC 7950] does not allow including YANG deviation statements in standard YANG modules because the actual definition of these YANG deviation statements is implementation specific. + +Implementations compliant with [ITU-T G.8021] can also implement some of the capabilities defined in [IEEE 802.1Q] even if not required by [ITU-T G.8021]. + +Implementations which are fully compliant with both [IEEE 802.1Q] and [ITU-T G.8021], do not need to report any deviation statement. + +This appendix provides some guidelines on how these deviation statements could be written by providing, as an example, the itut-eth-oam-deviation-example YANG module which can be used by implementations which are compliant only with [ITU-T G.8021] and do not support any of the capabilities defined in [IEEE 802.1Q] and not required in [ITU-T G.8021]. + +The itut-eth-oam-deviation-example YANG module contains also some deviation statements examples which are applicable only to implementations which are compliant with [ITU-T G.8021] and the 2006 Edition of [ITU-T G.8013]. These deviation statements should not be declared by + +implementations which are compliant with [ITU-T G.8021] and subsequent Editions of [ITU-T G.8013]. + +The zip file containing the YANG data model example used in this appendix is provided in clause 8.1. + +# Appendix IV + +## Mapping of the IEEE 802.1Q CFM and ITU-T G.8013 parameters + +(This appendix does not form an integral part of this Recommendation.) + +This appendix analyses and summarizes the comparison and mapping between the IEEE 802.1Q CFM parameters (i.e., the leaf nodes) and ITU-T G.8021 parameters (i.e., MI signal values). + +| ieee802-dot1q-cfm.yang | ITU-T G.8021 parameter | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cfm/maintenance-group/mep/inactive-remote-mep | Not supported in ITU-T. | +| cfm/maintenance-group/mep/mep-db/ rmep-failed-ok-time : ro mandatory | Not supported in ITU-T. | +| cfm/maintenance-group/mep/mep-db/ mac-address : ro mandatory | Not supported in ITU-T. | +| cfm/maintenance-group/mep/mep-db/ port-status-tlv : ro optional | Not supported in ITU-T.
It is optional. | +| cfm/maintenance-group/mep/mep-db/ interface-status-tlv : ro optional | Not supported in ITU-T.
It is optional. | +| cfm/maintenance-group/mep/continuity-check/ defect : 5 bits:
def-rdi-ccm, def-mac-status, def-remote-ccm, def-error-ccm, def-xcon-ccm | No cDEG, no cUNPr.
xcon-ccm is composition of cUNL and cMMG.
error-ccm is composition of cUNP and cUNM.
Proposal solution:
define an itu-defects leaf, with typedef ..., and describe the relationship of some of the bits with the 802.1 mep-defect-type. | +| cfm/maintenance-group/mep/ linktrace-reply | Not supported in ITU-T.
The itut-eth-oam:linktrace-state container has been defined to report the result of the latest OAM linktrace operation. | +| cfm/maintenance-group/mep/transmit-loopback/input: choice lbm-destination : rw mandatory | Conditional mandatory in ITU-T.
Not applicable for OAM loopbackDiscovery operation. | +| cfm/maintenance-group/mep/action: transmit-loopback/input: loopback-input-grouping: case dest-mep-id | Case dest-mep-id is not supported. | +| cfm/maintenance-group/mep/transmit-loopback/input: lbm-priority | In ITU-T, the default value of this attribute is the same as the CCM priority. | +| cfm/maintenance-group/mep/transmit-loopback/input: lbm-data-tlv | Not supported in ITU-T.
The eth-oam:data-tlv-length attribute has been defined to configure the length of the Data TLV. | +| cfm/maintenance-group/mep/action: transmit-loopback/output: leaf lbm-request-id | Not supported in ITU-T. | +| cfm/maintenance-group/mep/action: transmit-linktrace/input: linktrace-input-grouping: case target-mep-id | Not supported in ITU-T. | +| cfm/maintenance-group/mep/action: transmit-linktrace/input: linktrace-input-grouping: leaf ltm-flags | Not supported in ITU-T. | + +| ieee802-dot1q-cfm.yang | ITU-T G.8021 parameter | +|-------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | The Flag field of the transmitted LTM OAM Message is set by the system as specified in Figure 9.5-2 of [ITU-T G.8013]. | +| cfm/maintenance-group/mep/action: transmit-linktrace/output: ltm-transaction-id | Not supported in ITU-T. | +| cfm/maintenance-group/mep/action: transmit-linktrace/output: ltm-egress-identifier | Not supported in the 2006 Edition of [ITU-T G.8013] but supported by the later editions. | +| cfm/maintenance-group/mep/linktrace-reply/ | Not supported in ITU-T.
In [ITU-T G.8052.1], the linktrace-state container is defined instead to report the result of the latest linktrace operation, in compliance with [ITU-T G.8021]. | +| cfm/maintenance-group/mep/linktrace-reply/responses/ ltr-receive-order | Not supported in ITU-T. | +| cfm/maintenance-group/mep/linktrace-reply/responses/ ltr-last-egress-identifier | Not supported in the 2006 Edition of [ITU-T G.8013] but supported by the later editions. | +| cfm/maintenance-group/mep/linktrace-reply/responses/ ltr-next-egress-identifier | Not supported in the 2006 Edition of [ITU-T G.8013] but supported by the later editions. | +| cfm/maintenance-group/mep/linktrace-reply/responses/ ltr-relay | To check and verify whether this is the RelayAction field (see Figure 9.6-1 of [ITU-T G.8013]) | +| cfm/maintenance-group/mep/linktrace-reply/responses/ ltr-forwarded | Not supported in the 2006 Edition of [ITU-T G.8013] but supported by the later editions. | +| cfm/maintenance-group/mep/linktrace-reply/responses/ ltr-terminal-mep | Not supported in the 2006 Edition of [ITU-T G.8013] but supported by the later editions. | + +# Bibliography + +- [b-Eclipse-Papyrus] Papyrus Eclipse UML Modelling Tool +
(IPv6), clauses 2 and 3 of [IETF RFC 3032] | +| ETH client encapsulation | [ITU-T G.8110.1] | +| OAM encapsulation | [IETF RFC 5586] and [ITU-T G.8110.1] | + + + +Diagram illustrating the information flow relationship in MPLS-TP. It shows a Client connected to an MPLS-TP path (MT/CL, MT) which is connected to an MPLS-TP tunnel (MT/MT, MT) via MPLS-TP\_CIs. The tunnel is connected to a server (Srv/MT, Srv) via another MPLS-TP\_CI. The server is connected to a service (Srv) via Srv\_AIs, and finally to Srv\_CIs. The diagram is labeled G.8112-Y.1371(12)\_F6-6. + +**Figure 6-6 – Example of information flow relationship** +Srv: server + +#### 6.2.1.1 MPLS-TP OAM + +Figure 6-7 illustrates the generic format for MPLS-TP OAM. + +The MPLS-TP OAM header consists of an MPLS-TP generic associated channel label (GAL) as specified in [IETF RFC 5586]. The MPLS-TP OAM payload consists of a generic associated channel (G-ACh) header, the associated channel header time, length and value (ACH TLV; optional), and G-ACh message. MPLS-TP OAM packets are distinguished from user data packets using the OAM header. Specific formats for MPLS-TP OAM lie outside the scope of this Recommendation. + + + +Diagram showing the generic format for MPLS-TP OAM. It displays a packet structure with fields: LABEL (13), TC, S (1), and TTL (1) in the header; and G-ACh header, ACH TLV Header and ACH TLV (if present), and G-ACh message in the payload. Below the fields, the header is labeled 'OAM Header' and the payload is labeled 'OAM Payload'. The diagram is labeled G.8112-Y.1371(12)\_F6-7. + +**Figure 6-7 – Generic format for MPLS-TP OAM** + +#### 6.2.1.2 Payload headers + +##### 6.2.1.2.1 ETH payload header + +The mapping ETH payload header is described in clause 7.1 of [ITU-T G.8110.1]. + +### 6.2.2 MPLS-TP link frames + +#### 6.2.2.1 ETH link frame + +The MPLS-TP\_CI traffic unit (see [ITU-T G.8110.1]) is extended with a 3-bit traffic class (TC) field, a 20-bit label to complete the shim header. The resulting MPLS-TP labelled packet is then mapped as specified in [IETF RFC 3032], clauses 5 and 6.1 of [ITU-T G.8012] into the ETH payload information field using type encapsulation. + +With the type encapsulation, the MAC destination address (DA), MAC source address (SA) and type fields are prepended. The MAC DA can be the MAC address of the MPLS-TP interface of the next hop or the broadcast MAC address (see [IETF RFC 7213]). The MAC SA is the the MAC address of the sending interface. The type has value 0x8847. The frame check sequence (FCS) field specified in section 3 of [IEEE 802.3] with a 32-bit cyclic redundancy check (CRC) is appended. See Figure 6-8. + + + +The diagram illustrates the hierarchical encapsulation of data into an Ethernet frame. It shows five layers of encapsulation from top to bottom: + +- MPLS-TP\_CI traffic unit:** The top layer, containing 'S' (Stack indicator), 'TTL' (Time to Live), and 'Payload'. +- MPLS-TP labelled packet:** The second layer, adding a 'Label' (20 bits) and 'TC' (3 bits) to the MPLS-TP\_CI traffic unit. +- EtherType encapsulated client:** The third layer, adding a 'Type' field to the MPLS-TP labelled packet, resulting in 'Client data'. +- ETH:** The fourth layer, adding 'DA' (Destination Address), 'SA' (Source Address), and 'PAD' (Padding) to the Client data, resulting in an 'MSDU' (MAC Service Data Unit). +- MAC frame:** The bottom layer, adding 'PA' (Preamble) and 'SFD' (Start Frame Delimiter) to the MSDU, and appending an 'FCS' (Frame Check Sequence). + +The diagram uses dashed lines to indicate the boundaries of the encapsulated units. The label 'G.8112-Y.1371(12)\_F6-8' is present at the bottom right. + +Diagram of Type encapsulation ETH link frame structure + +Figure 6-8 – Type encapsulation ETH link frame + +#### 6.2.2.2 GFP-F link frame + +The MPLS-TP\_CI traffic unit (see [ITU-T G.8110.1]) is extended with a 3-bit TC field, a 20-bit label to complete the shim header. The resulting MPLS-TP labelled packet is then mapped as specified in clause 7.6 of [ITU-T G.7041] in the generic framing procedure (GFP) payload information field. A core header with payload length indicator (PLI) and core header error check (cHEC) fields and a payload header field with payload type identifier (PTI), payload frame check sequence indicator (PFI), extension header identifier (EXI), user payload identifier (UPI) and type header error check (tHEC) subfields are prepended. The PTI subfield has value 000, the PFI subfield has value 1, the EXI subfield has value 0000 and the UPI subfield has value 0x0D. A payload FCS field with a 32-bit CRC is appended. See Figure 6-9. The maximum size of the GFP payload information field is specified in clause 6.1.2 of [ITU-T G.7041]. + + + +PLI + cHEC + PTI = 000 + PFI = 1 + EXI = 0000 + UPI = 0x0D (unicast) + tHEC = 0xD2DE (unicast) + +G.8112-Y.1371(12)\_F6-9 + +Diagram of GFP-F link frame structure showing nested MPLS-TP units. The outermost frame is a GFP-F frame with Core header, Payload header, GFP payload information field, and Payload FCS. Inside the GFP payload information field is an MPLS-TP labelled packet with Label, TC, and MPLS-TP\_CI. Inside the MPLS-TP\_CI is an MPLS-TP traffic unit with S, TTL, and Payload. Below the diagram, fields are defined: PLI, cHEC, PTI = 000, PFI = 1, EXI = 0000, UPI = 0x0D (unicast), tHEC = 0xD2DE (unicast). Reference G.8112-Y.1371(12)\_F6-9 is noted. + +**Figure 6-9 – GFP-F link frame** + +Figure 6-10 illustrates the mapping of the bits in the MPLS-TP labelled packet into the GFP payload information field within the generic framing procedure – frame-mapped (GFP-F) frame. + + + +G.8112-Y.1371(12)\_F6-10 + +Detailed mapping diagram showing how an MPLS-TP labelled packet is mapped into a GFP-F frame. On the left, the MPLS-TP packet structure is shown with Label (20 bits), TC (3 bits), S (1 bit), TTL (8 bits), and Payload. On the right, the GFP payload information field structure is shown with PLI (16 bits), cHEC (16 bits), PTI (8 bits), UPI (16 bits), tHEC (16 bits), and Payload FCS (32 bits). Arrows show the mapping of MPLS-TP fields into GFP fields: Label into GFP payload information field, TC and S into GFP payload information field, TTL into GFP payload information field, and Payload into GFP payload information field. Reference G.8112-Y.1371(12)\_F6-10 is noted. + +**Figure 6-10 – Mapping MPLS-TP labelled packet into GFP-F link frame** + +### **6.2.3 MPLS-TP control frames** + +MPLS-TP control plane communication (NNIc) for signalling and routing purposes is used for signalling communication network (SCN) links. + +Four alternatives for SCN links are specified in [ITU-T G.7712]: + +- SCN link sharing a server layer trail with MPLS-TP user traffic; +- SCN link utilizing the MPLS-TP signalling communication channel (SCC); +- SCN link utilizing a dedicated MPLS-TP LSP; +- Separate and independent SCN link. + +When an SCN link shares a server layer trail, MPLS-TP control frames are encapsulated either in IPv4 or in IPv6 or in open systems interconnection (OSI) network layer packets and sent natively on the MPLS-TP NNI. See Figure 6-11. + +NOTE – The encapsulation of the MPLS-TP control frames into IPv4, IPv6 or OSI network layer (OSINL) packets lies outside the scope of this Recommendation. + + + +G.8112-Y.1371(12)\_F6-11 + +Diagram illustrating the encapsulation of MPLS-TP control frames over shared trail SCN links. The diagram shows three layers of encapsulation. At the top, an OSINL packet is shown with a 'PDU header' and 'Data'. Below it, an IPv4 or IPv6 packet is shown with an 'IP header' and 'Payload'. At the bottom, a 'Link frame' is shown with a 'Link header' and 'Link trailer'. Dashed lines indicate that the 'Data' from the OSINL packet is encapsulated into the 'Payload' of the IPv4/IPv6 packet, which is then encapsulated into the 'Link frame'. + +**Figure 6-11 – MPLS-TP control frame over shared trail SCN links** + +Additional control frames can be required by the specific encapsulation method used for sending MPLS-TP link frames. + +MPLS-TP control frames are distinguished from MPLS-TP data frames because they are not MPLS-TP link frames: the multiplexing of MPLS-TP and non-MPLS-TP link frames is required on all the MPLS-TP NNIs. + +The encapsulation method used for MPLS-TP control frames is the same as that used for MPLS-TP link frames. + +#### 6.2.3.1 GFP-F link frame + +The signalling and routing message is encapsulated into either IPv4 or IPv6 or OSI connectionless network layer service (CLNS) (intermediate service-intermediate service; IS-IS) packet as described in [ITU-T G.7712]. + +When the MPLS-TP NNI uses the GFP-F encapsulation, there are no other control protocols defined. + +Control packets are encapsulated as specified in the standard references of Table 6-5 in the GFP payload information field. A core header with PLI and cHEC fields and a payload header field with PTI, PFI, EXI, UPI and tHEC subfields are prepended. The PTI subfield has value 000, the PFI subfield has value 1, the EXI subfield has value 0000 and the UPI subfield has the values defined in Table 6-3. A payload FCS field with a 32-bit CRC is appended. + +**Table 6-3 – Overview of GFP-F encapsulated control packets** + +| Encapsulation type | Reference | UPI value | +|-----------------------------------|--------------------------------------|-----------| +| IP control packets | (IPv4) clause 7.7 of [ITU-T G.7041] | 0x10 | +| | (IPv6) clause 7.7 of [ITU-T G.7041] | 0x11 | +| OSI network layer control packets | (OSINL) clause 7.7 of [ITU-T G.7041] | 0x0F | + +### 6.2.4 MPLS-TP NNI + +The MPLS-TP NNI is supported by the interfaces listed in clauses 6.2.4.1 to 6.2.4.4. + +#### 6.2.4.1 MoE NNI + +The MoE NNI deploys the type encapsulation-based ETH link frame as specified in clause 6.2.2.1. + +#### 6.2.4.2 MoS NNI + +The MoS NNI deploys the GFP-F link frame as specified in clause 6.2.2.2. The mapping of the GFP-F link frames into VC-11/VC-11-Xv, VC-12/VC-12-Xv, VC-3/VC-3-Xv and VC-4/VC-4-Xv) and a virtual concatenated virtual container-order 4 (VC-4-Xc) is specified in clause 10.6 of [ITU-T G.707]. Path overhead and virtual concatenation of the virtual containers (VCs) is specified in [ITU-T G.707]. The components of the MoS NNI using the default encapsulation are illustrated in Figure 6-12. + + + +Figure 6-12: Components of the MoS NNI using GFP-F encapsulation. The diagram shows a stack of layers. At the top is a pink layer labeled 'MPLS-TP'. Below it is a blue layer labeled 'VC-m, VC-m-Xv'. Below that is a green layer labeled 'VC-n'. To the right of the green layer are two more green blocks labeled 'VC-n-Xv' and 'VC-4-Xc'. A label 'GFP' with an arrow points to the boundary between the MPLS-TP and VC-m layers. A small text 'G.812-Y.1371(12)\_F6-12' is at the bottom right. + +Figure 6-12 – Components of the MoS NNI using GFP-F encapsulation + +#### 6.2.4.3 MoO NNI + +The MoO NNI deploys the GFP-F link frame as specified in clause 6.2.2.2 and its components are illustrated in Figure 6-13. The mapping of the GFP-F link frame into optical channel data unit-order j/optical channel data unit-order k (ODUj/ODUk) is specified in clause 17.4 of [ITU-T G.709]. Path overhead of the optical channel data units (ODUs) is specified in [ITU-T G.709]. + + + +Figure 6-13: Components of the MoO NNI. The diagram shows a stack of layers. At the top is a pink layer labeled 'MPLS-TP'. Below it is a yellow layer labeled 'ODUj'. Below that is a yellow layer labeled 'ODUk'. A label 'GFP' with an arrow points to the boundary between the MPLS-TP and ODUj layers. A small text 'G.812-Y.1371(12)\_F6-13' is at the bottom right. + +Figure 6-13 – Components of the MoO NNI + +#### 6.2.4.4 MoP NNI + +The MoP NNI deploys the GFP-F link frame as specified in clause 6.2.2.2. + +The mapping of the GFP-F link frames into P11s/P11s-Xv, P12s/P12s-Xv, P31s/P31s-Xv and P32e/P32e-Xv is specified in [ITU-T G.8040]. + +The frame structure of P11s, P12s and P32e is specified in [ITU-T G.704], the frame structure of P31e, the 34 368 kbit/s PDH path layer according to [ITU-T G.705], is specified in [ITU-T G.951] and the frame structure of P31s is specified in [ITU-T G.832]. Virtual concatenation of the P11s, P12s, P31s and P32e signals is specified in [ITU-T G.7043]. + +For the channelized P32e, the direct multiplexing of P11s into P32e is specified in clause 9.3 of [ANSI T1.107]. + +Figure 6-14 illustrates the relation of the components of MoP NNI using GFP-F. + + + +Diagram of MoP NNI components using GFP-F. At the top is a large pink rectangle labeled 'MPLS-TP'. Below it is a blue rectangle labeled 'GFP'. Below the GFP rectangle is a row of eight green rectangles labeled from left to right: P32e, P32e-Xv, P11s, P11s-Xv, P31s, P31s-Xv, P12s, and P12s-Xv. A callout line labeled 'GFP' points to the blue rectangle. A small text label 'G.8112-Y.1371(12)\_F6-14' is in the bottom right corner. + +**Figure 6-14 – Components of the MoP NNI using GFP-F** + +## 6.3 MPLS-TP labels + +In the label field of the shim header for MPLS-TP connection identification, 20 bits are available. Some of these values are pre-assigned. The interpretation of these values is as described in Table 6-4. + +**Table 6-4 – MPLS-TP label value interpretation** + +| MPLS-TP label value | Interpretation | +|---------------------|------------------------------------------------------------------------------| +| 0-3 | Defined in [IETF RFC 3032]; not used in MPLS-TP | +| 4-12 | Reserved for future standardization (Note) | +| 13 | Defined in [IETF RFC 5586] | +| 14 | Defined in [ITU-T Y.1711]; not used in MPLS-TP | +| 15 | Reserved for future standardization (Note) | +| 16-1 048 575 | MPLS-TP connection identifier range (values assigned as per [IETF RFC 3031]) | + +NOTE – The Internet Assigned Numbers Authority (IANA) allocates these values through the Internet Engineering Task Force (IETF) consensus action process. + +## 6.4 MPLS-TP shim header + +The MPLS-TP traffic unit includes one or more MPLS shim headers as defined in [IETF RFC 3031] and specified as label stack entry in section 2 of [IETF RFC 3032]. + +# 7 Multiplexing/mapping principles + +Figure 7-1 shows the relationship between various information structure elements and illustrates the multiplexing structure and mappings for the MPLS-TP from client signal to link frames. It illustrates an n-level multiplexing of MPLS-TP signals into MPLS-TP LSP. The MPLS transport profile characteristic information (MT\_CI) traffic is multiplexed into an MPLS-TP unit group level 1 (MUG1). The MUG1 is extended with a second level MPLS shim header and then multiplexed into a higher MUG level. + + + +The diagram illustrates the mapping and multiplexing process for MPLS-TP. On the left, client signals (ETH, GFP-F, PPP/HDLC) are shown. These are mapped into an MPLS-TP LSP, which is then multiplexed into a Tunnel. The Tunnel is further multiplexed into a MU (Mux) unit. The MU unit is connected to an OAM (Operations, Administration, and Management) block. The diagram also shows the reverse process: OAM being mapped into a MU unit, which is then multiplexed into a Tunnel, which is then mapped into an MPLS-TP LSP. The LSP is then mapped into a Payload header, which is then mapped into Non-IP traffic. The diagram includes labels for Shim header, MPLS-TP LSP, Tunnel, MU, MUxGn, OAM, IP, and Non-IP. The diagram is labeled G.8112-Y.1371(12)\_F7-1. + +Diagram illustrating MPLS-TP mapping, multiplexing, and segment monitoring. The diagram shows client signals (ETH, GFP-F, PPP/HDLC) being mapped into an MPLS-TP LSP. The LSP is then multiplexed into a Tunnel, which is further multiplexed into a MU (Mux) unit. The MU unit is connected to an OAM (Operations, Administration, and Management) block. The diagram also shows the reverse process: OAM being mapped into a MU unit, which is then multiplexed into a Tunnel, which is then mapped into an MPLS-TP LSP. The LSP is then mapped into a Payload header, which is then mapped into Non-IP traffic. The diagram includes labels for Shim header, MPLS-TP LSP, Tunnel, MU, MUxGn, OAM, IP, and Non-IP. The diagram is labeled G.8112-Y.1371(12)\_F7-1. + +Figure 7-1 – MPLS-TP mapping, multiplexing and segment monitoring + +## 7.1 Mapping + +The client signal is mapped into the MPLS-TP LSP directly (like IP clients). For non-IP clients like Ethernet, a CW is optionally used as referred to in [ITU-T G.8110.1]. The CW is also known as the CII in [ITU-T Y.1415]. + +MPLS-TP OAM (see clause 6.2.1.1) may be added and both data and OAM packets are extended with a shim header (see clause 6.4). + +The MPLS-TP packets are then mapped into the applicable link frames as specified in clause 6.2.2 and those link frames are transported over an MPLS-TP topological link. + +## 7.2 MPLS-TP multiplex + +The label-stacking mechanism in MPLS-TP provides an n-level MPLS-TP LSP multiplexing capability. The 20-bit label in the shim header identifies the individual MPLS-TP tributaries within the aggregate (MPLS-TP tunnel) signal. Up to $2^{20}$ MPLS-TP tributaries can be supported in the aggregate signal. + +## 7.3 MPLS-TP tandem connection monitoring + +Multiplexing may not be performed in all stacking steps to support one or more levels of MPLS-TPT [sub-path maintenance element (SPME)] as described in [ITU-T G.8110.1]. + +# 8 Physical specification of the MPLS-TP interfaces + +There are no dedicated MPLS-TP physical interfaces. MPLS-TP interfaces are supported by physical interfaces specified in the following transport technologies: PDH, SDH, OTH and Ethernet. + +# Appendix I + +## Example of layer networks in ETH UNI and MPLS-TP NNI + +(This appendix does not form an integral part of this Recommendation.) + +[ITU-T G.8110.1] defines Ethernet as the client of MPLS-TP. Ethernet UNI and NNI are defined in [ITU-T G.8012]. The ETH UNI, ETH NNI and MPLS-TP NNI encompass multiple layer networks, each with its dedicated UNI and NNI (Figure I.1). The Ethernet PHY layer (ETY) UNI is defined in [ITU-T G.8012]. + + + +The diagram illustrates the layer networks in ETH UNI and MPLS-TP NNI. It shows a stack of layers: ETH, ETY, MPLS-TP, and multiple service layers (SrvA, SrvB, SrvC). Interfaces are labeled as ETH UNI, ETY UNI, ETH NNI, MPLS-TP NNI, SrvA NNI, SrvB NNI, and SrvC NNI. The diagram shows two main stacks connected by a central MPLS-TP layer. The left stack has ETH and ETY layers connected via ETH UNI and ETY UNI to an internal ETH and ETY layer. The right stack is similar. Between them, the MPLS-TP layer is connected via ETH NNI and MPLS-TP NNI. Below the MPLS-TP layer, there are three service layers: SrvA, SrvB, and SrvC. Each service layer is connected via its respective NNI (SrvA NNI, SrvB NNI, SrvC NNI) to a central set of service layers. The central set of service layers is connected to the right stack via its respective NNI. The diagram is labeled G.8112-Y.1371(12)\_Fl.1. + +Diagram illustrating the layer networks in ETH UNI and MPLS-TP NNI. The diagram shows a stack of layers: ETH, ETY, MPLS-TP, and multiple service layers (SrvA, SrvB, SrvC). Interfaces are labeled as ETH UNI, ETY UNI, ETH NNI, MPLS-TP NNI, SrvA NNI, SrvB NNI, and SrvC NNI. The diagram shows two main stacks connected by a central MPLS-TP layer. The left stack has ETH and ETY layers connected via ETH UNI and ETY UNI to an internal ETH and ETY layer. The right stack is similar. Between them, the MPLS-TP layer is connected via ETH NNI and MPLS-TP NNI. Below the MPLS-TP layer, there are three service layers: SrvA, SrvB, and SrvC. Each service layer is connected via its respective NNI (SrvA NNI, SrvB NNI, SrvC NNI) to a central set of service layers. The central set of service layers is connected to the right stack via its respective NNI. The diagram is labeled G.8112-Y.1371(12)\_Fl.1. + +Figure I.1 – Example of layer networks in ETH UNI and MPLS-TP NNI + +# Appendix II + +## Bandwidth requirements for MPLS-TP transport + +(This appendix does not form an integral part of this Recommendation.) + +This appendix shows the transport bandwidth requirements for ETH client encapsulation over MPLS-TP over ETH link as a function of the Ethernet MAC rate, the client payload field length, whether or not the network has inserted a virtual local area network (VLAN) tag. This is shown in Tables II.1 and II.2. + +NOTE – The MAC bit rate in Table II.1 is the actual bit rate of the Ethernet MAC frames after the removal of the 12 byte inter-packet gap plus 7 byte preamble + 1 byte start of frame delimiter (SFD). In other words, MAC bit rate = (Ethernet interface rate) (number of bits in the MAC frame)/(number of bits in the MAC frame + 12 byte inter-packet gap + 7 byte preamble + 1 byte SFD). The calculations in Table II.2 are the same except that 10 Gbit Ethernet uses a 5 byte minimum inter-packet gap instead of 12 bytes. + +**Table II.1 – Maximum (un)tagged MAC bit rate per "1 Gbit/s" MAC server signal** + +| | | Payload bit rate (bit/s, nominal bit rate for Ethernet) | | | | | | +|----------|------------------|---------------------------------------------------------------------------|-------------------------|---------------|-----------------------------------------------------------------------------------|-------------------------|---------------| +| | | 1 000 000 000 | | | 1 000 000 000 | | | +| | | MAC bit rate (kbit/s), throughput (%)
relative to maximum MAC bit rate | | | Packets per second (pps), throughput (%)
relative to maximum packet per second | | | +| VLAN tag | MAC-size (Bytes) | 1000Base-X | MPLS-TP over 1000Base-X | Throughput, % | 1000Base-X | MPLS-TP over 1000Base-X | Throughput, % | +| 0 | 64 | 761.905 | 581.818 | 76.36 | 1.488.095 | 1.136.364 | 76.36 | +| 0 | 128 | 864.865 | 735.632 | 85.06 | 844.595 | 718.391 | 85.06 | +| 0 | 256 | 927.536 | 847.682 | 91.39 | 452.899 | 413.907 | 91.39 | +| 0 | 512 | 962.406 | 917.563 | 95.34 | 234.962 | 224.014 | 95.34 | +| 0 | 1 024 | 980.843 | 957.009 | 97.57 | 119.732 | 116.822 | 97.57 | +| 0 | 1 518 | 986.996 | 970.588 | 98.34 | 81.274 | 79.923 | 98.34 | +| 0 | 9 618 | 997.925 | 995.240 | 99.73 | 12.969 | 12.935 | 99.73 | +| 1 | 64 | 772.727 | 596.491 | 77.19 | 1.420.455 | 1.096.491 | 77.19 | +| 1 | 128 | 868.421 | 741.573 | 85.39 | 822.368 | 702.247 | 85.39 | +| 1 | 256 | 928.571 | 849.673 | 91.50 | 446.429 | 408.497 | 91.50 | +| 1 | 512 | 962.687 | 918.149 | 95.37 | 233.209 | 222.420 | 95.37 | +| 1 | 1 024 | 980.916 | 957.169 | 97.58 | 119.275 | 116.387 | 97.58 | +| 1 | 1 518 | 987.030 | 970.663 | 98.34 | 81.064 | 79.719 | 98.34 | +| 1 | 9 618 | 997.926 | 995.242 | 99.73 | 12.964 | 12.929 | 99.73 | + +NOTE 1 – VLAN tag; value gives the number of VLAN tags (no VLAN tag = 0). + +NOTE 2 – Encapsulation overhead; 20 bytes for physical Ethernet interface [7 byte preamble, 1 byte SFD and 12 byte minimum interpacket gap (IPG)]. 26 byte encapsulation overhead for ETH client over MPLS-TP with CW. + +**Table II.2 – Maximum (un)tagged MAC bit rate +per "10 Gbit/s" MAC server signal** + +| | | Payload bit rate (nominal bit rate for Ethernet) | | | | | | +|-----------------|-------------------------|-------------------------------------------------------------------------------|-------------------------------|----------------------|---------------------------------------------------------------------------------------|-------------------------------|----------------------| +| | | 10 000 000 000 | 10 000 000 000 | 1 000 000 000 | 1 000 000 000 | | | +| | | MAC bit rate (kbit/s), throughput (%) relative to maximum MAC bit rate | | | Packets per second (pps), throughput (%) relative to maximum packet per second | | | +| VLAN tag | MAC-size (Bytes) | 10GBase-R | MPLS-TP over 10GBase-R | Throughput, % | 10GBase-R | MPLS-TP over 10GBase-R | Throughput, % | +| 0 | 64 | 7.619.048 | 5.818.182 | 76.36 | 14.880.952 | 11.363.636 | 76.36 | +| 0 | 128 | 8.648.649 | 7.356.322 | 85.06 | 8.445.946 | 7.183.908 | 85.06 | +| 0 | 256 | 9.275.362 | 8.476.821 | 91.39 | 4.528.986 | 4.139.073 | 91.39 | +| 0 | 512 | 9.624.060 | 9.175.627 | 95.34 | 2.349.624 | 2.240.143 | 95.34 | +| 0 | 1 024 | 9.808.429 | 9.570.093 | 97.57 | 1.197.318 | 1.168.224 | 97.57 | +| 0 | 1 518 | 9.869.961 | 9.705.882 | 98.34 | 812.744 | 799.233 | 98.34 | +| 0 | 9 618 | 9.979.249 | 9.952.401 | 99.73 | 129.695 | 129.346 | 99.73 | +| 1 | 64 | 7.727.273 | 5.964.912 | 77.19 | 14.204.545 | 10.964.912 | 77.19 | +| 1 | 128 | 8.684.211 | 7.415.730 | 85.39 | 8.223.684 | 7.022.472 | 85.39 | +| 1 | 256 | 9.285.714 | 8.496.732 | 91.50 | 4.464.286 | 4.084.967 | 91.50 | +| 1 | 512 | 9.626.866 | 9.181.495 | 95.37 | 2.332.090 | 2.224.199 | 95.37 | +| 1 | 1 024 | 9.809.160 | 9.571.695 | 97.58 | 1.192.748 | 1.163.873 | 97.58 | +| 1 | 1 518 | 9.870.298 | 9.706.633 | 98.34 | 810.636 | 797.194 | 98.34 | +| 1 | 9 618 | 9.979.257 | 9.952.420 | 99.73 | 129.641 | 129.293 | 99.73 | + +NOTE 1 – VLAN tag; value gives the number of VLAN tags (no VLAN tag = 0). + +NOTE 2 – Encapsulation overhead; 20 bytes for physical Ethernet interface (7 byte preamble, 1 byte SFD and 12 byte minimum IPG). 26-byte Encapsulation overhead for ETH client over MPLS-TP with CW. + +# Bibliography + +- [b-ITU-T G.8110.1] Recommendation ITU-T G.8110.1/Y.1370.1 (2011), *Architecture of the multi-protocol label switching transport profile layer network.* + + + +# 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.3599 | +| BIG DATA | Y.3600–Y.3799 | +| QUANTUM KEY DISTRIBUTION NETWORKS | Y.3800–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.8121.1-201811-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6992c32f03b5eff62ac5be98028f14196668a84b --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58aa1dd543103bae5a8bf0a69ff3aaa73db0862df823de80c2994bda5830f9da +size 78806 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b42342f9162c5025cff9a86925af2992d0b0c56 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51e091a1d97324de18b0caaa1a94b6b6171757c1a0fe5de99d1dcad4f122bb88 +size 26514 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ab4f18ab5f947423f095fcd53435dd5ced78e6a --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c009549afbb83d5ff5739610ac34f91eebaf23056181b68f7e71f18753d8d4a +size 21859 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..670cc110f5b84ed20027e57451906f9a5dd8c000 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d09645ff2af7d861eb33bc2ec080230745a8b775c56d51a7eecff9874f6447d7 +size 23143 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18738f9144f340293db5868e7a4c6fa9cb616274 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c4b36a5f453c048a8a7d47646cfeddc705b71876e907995bf2187192d53406c +size 139910 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/10b0dda884baae493ad958422d11b552_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/10b0dda884baae493ad958422d11b552_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..904b616bd2446bbf79ee6e65e6ae946d913c8c15 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/10b0dda884baae493ad958422d11b552_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a4ef1000ea808fcf917e0e733324db69fb3293da46d10d53635115b6b81aff9 +size 48161 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..125d0c5cabab8b20f4cf41fc435e6028995144b0 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9fdad7acb7423fa0f5b35f605e41a49f8cfaa79ea913de816cf1b961e3a38df +size 115463 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4691f9c995e38fc4708eb39d8197899b013db1c --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23d4e4a894977a58286e32db7c2197e52e1360419fcc05f5f2c34de8b18c009f +size 64405 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf806adcc80ea1761d7173d160dd1abfead0ef2d --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6741452b561af10fdb8c98f8658d9fc1f6ad4cd26cec5deb2fa9fdc0b9446b8 +size 51574 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..405bfdbf5fd33f3491fe67bbbf68571260848714 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b238441d33914f5ae35e6595f82d1e29a6584e0c39e921817de96bf9cc2e03fc +size 27538 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a82a1b86f9d767cdd5568c75efee6af90abc418 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2eec446ad8123be6bb310278fe8d9b7ec6c33b21227b1471f4572c93eac1256 +size 25742 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/18d7d8de298d79e7bc87af5217f11203_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/18d7d8de298d79e7bc87af5217f11203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d5d56b0f1431f1238a23337d81358115e0384d2 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/18d7d8de298d79e7bc87af5217f11203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3264c0f34c6f32519537f289f9e9364c4917cf58469ea1714827b00daf2ce583 +size 12455 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1bc3cc1f2e87a2b340a2a24639e76b31125c7a0 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19c99b52241692a8d27ca46fa81b030d2615d4e13d50e31bb3767b536ff94a03 +size 10113 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fd1b3677024990458637f7504e26701fa3460f1 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36b13f1f72ccab5ae55dedd1716363a2bd581ad38909c4810c98be75af7a6e8f +size 118289 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd9764a4a872b56d02fbd840a1e3f2d841147788 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cee6adb0e55b4f5ef4927fec9b2bad023e8f57756c45f4e6e6469f9370177b67 +size 115464 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09114a20ceda6e4884f70f0e3c5f35a983a414f7 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ea9802107c473db8513afaaf2646701eac66ee9cfcbd3f5dd19a34cf28b6f57 +size 49185 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccb27bc8dbb08a60316510c2887e2631452c5361 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a304e1a2fc3c59ee7b9f247b60417861010cc32a84c0e23a7c325e53e668165 +size 117002 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/28f2f470a7b2446ae5f525123534383c_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/28f2f470a7b2446ae5f525123534383c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8a946f7fdf987af92178f8e7faacc2bfcf41fae --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/28f2f470a7b2446ae5f525123534383c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0510c3fc4e23fae7fb866448b9054cb46a4c6a708a2cdd7869a2f00c3ba6afa +size 26481 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ea0479736d7e8622122621c4d83fd6e614b843d --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3019d07f604bfe7d9a1645de603a76a6a2d3bb261b422f911df1926455ad15ef +size 127098 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/2bc39576969969ffe6d3f3d5264bba75_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/2bc39576969969ffe6d3f3d5264bba75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2ca13fe28c8efd7f581cab05c386bbcc2037163 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/2bc39576969969ffe6d3f3d5264bba75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fcb62de2025e62af833059daa7b787fd2596cd2efdd86ec7c0cbfb32d97d833 +size 24281 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7024a930ff2f043588a8101c45b9f4d2ca3a79df --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1658595e43bc75f4e565b75b5cca198c8dfe39f6bdc4eaf6c8f6bd6adc95bb0 +size 100484 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed5b34352d38a18a15a79a302faa2ca17599d26b --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2bf97298a68d6c14f41acf30cdf043855e5f43a39751867a78524cd5ad77aa5 +size 89809 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2170363efd2d6d7893a3112e6ebe62eda023dc3 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd12e5bbe9ebda4911ead75f5e20ebb01198b531d530201fd49c3355d4d3bc45 +size 92952 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..307008597221318f39ffd46bc4be4a2c46fef883 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02b986b95b0f3aff7f9e4c8647834d17f2a451069950cc34d0a528aef8d64f6a +size 24088 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/38331e6e38fda222ecacad7292694c84_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/38331e6e38fda222ecacad7292694c84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eae9f6d9affc231623ccfe8abaa96147ffdd0aa8 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/38331e6e38fda222ecacad7292694c84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d55b373938e21fd9ff7e239de8c7979ab8d066f7bc83fdc21247162e5246a9e2 +size 14727 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aced2cd63f43be33339573290044ebc57a8eec73 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05ce0e0402e19a12ed0de99ad4527c779a0d5763c8f0d814f07b420f58ffb47d +size 21625 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61f45e0b965c1b1fcf759dc0343e2046ad805c6a --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28642754ecb3d0617401453f7f43a9c6745df441b7e4fad6f18bd117ad447372 +size 26756 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f08d5bce34954fad4c9e65c40827ad10b5b43b9d --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:523f258fd70acf68e12879ee94edfb654ad53da29e00edb55c3a0e2caa7ea09b +size 10060 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd361c5fffbf3f9c1866f7897544b12fd2d1095e --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:031a6069972aec73879aa4c2657aeefecf5b4dffeee611a4c19babf83996cc13 +size 26824 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b8495984223df1a9d1185ea9339b57346e9c2ef --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d699e945ba1faccc72055a11b5c321baf1a093357b25f6d81bb252ca9a494db +size 27131 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20a31426f094aca2a57bbb1189f90e6bd1b8349d --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4f497fd3b17c89937f65d28d92d0a60b5f75c798e5bd4c233123550d192b312 +size 27230 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b517a824fad8f1d2b1f8d2672f88d7817f52e025 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66ec69604790c3ee243893a74962795c57947362237e3dc1dfd039b661043eba +size 34847 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8e777fee706ffd111029fe8db48fbd06c0f6e3a --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9c833d66a29d7129422bcff0b67f8b7791f30260f9a6894cc34273a511bfdf2 +size 96089 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56b95edb2512726ef76db2b8a641939158558736 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c46a968f14b7b714e73edc3fad0fa08fea0cfa8ceaf8a0bcd594775fa3549de0 +size 25873 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e94a4ea079b025fd940180f69831860decdb2010 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:163b4246eece371e8019ca07bb1bd424beea3a6e69a08747d5af8aed4cb7d2d3 +size 81606 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee27ac74237432c57e4053a64ca39cbcb0b45922 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42aa21dbf6667c62c576cb4b66379b06c8b255add43bd0757e4fdcce24772684 +size 24897 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..931219c0bff4acdda0ab13f5c442e86bdd2cd8bd --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ee7c7a8b85c7ecf4696d79d0716aebcae762a5a96868a018801a42dcc60e553 +size 26374 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a9feefdbf56afe29bc5409f14fde6e3c9c036ce --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12af42a7211396f49bf628e22d5389493bc2a9fcbe3b0b52c922d5f3506e38c1 +size 95686 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecaaf0616a46fab0caa871d43b2a4e3fa08f3084 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:202e55b64085eef9c9b1b658b83c58d162578cb7ff6784eaac73674dad7cee2f +size 83704 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c866c8b93c450367eda0897f7207a6c1621a8d0 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74f255cdd3782514b624a91506409188cd1176c01f41d3910f5516a46f631064 +size 92406 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87b6880dfaf18a0cd0c4f2d48b8384f364de1144 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97292a114a4d08ae65bdc10bca46fedfe6b4eb2a25f7b96ba17831b7bb94d594 +size 97285 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fa93f872241f06ee1f5ca3008f0411131744ebc --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13144e0090dce08c07e97b4615337a5f4a9be0f22b42f9041e504a04abbb98e7 +size 121836 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61c5a925d878fe4309317ec2d8cc52caf20c498e --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8d94e448d509d77b784ec18e8d05d4b22b3e5d623d89d72e0a19ce8ab62dbde +size 55087 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94f4022178bb2806663a454ebac12f93bcbaf00f --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0acb58b6e0e924c74af501b754cd9b93aa39bde6aca734d5539208a56d5cc0d3 +size 68795 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d66af65db5801e3b76cfcdc838b5773be6138e72 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:291c9589ed7cc0443b0d337fc11e5052c3672fe2ffa5d348401dcf0305a2129f +size 100001 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14169f6a453906627105d6176cd1afce6822cfcf --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e471eb47d63ee5b8acf7597969ff376a4da123417fcdbcab1a63c1ec532b1c4 +size 21879 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b0b261491b3786594f41210cc7908fa8ac3871f --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:871a73508374ddddf42ab0d781f16c1bbaa497ac70503919616340e22e88abea +size 32857 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13ea9b973b7315583bc5ee2233dcfd97f0eb2153 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db8a15b53669363410027f394ae9279e226446ebad4d30685675a21cfb10f78b +size 27301 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c260fc679dc06d91718fb63a098096fe6170e32 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f682e8fd11a389b29d77731895b1298d078c2a1bccbe9c844b95326e909ebfa4 +size 22896 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99245940e6a43a62be171e036a532aea5a953440 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cda892a713625065ec30f7163002a90c438414b622f8ef66ac3263a5352aee3d +size 142944 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f021dbe0e29196600eab356e84dd17043d82baaa --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d98ce0b69f12f41f4c8d32957d880cc8ce1c4a15cc87f38fff9f600abe63026 +size 87943 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/9afb9b6f1032f9571efb7260ca75d7cf_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/9afb9b6f1032f9571efb7260ca75d7cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd85c5f0cf29767d5fce2cdb865aece52387c01d --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/9afb9b6f1032f9571efb7260ca75d7cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09082581f21d9548df66739aba3c0950a4cd19b319365b8f1c69a3129a386b3c +size 4070 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79914ae7fb91819d0f2e520b14d24864675643b2 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10ac01b7bf7ab99de9f9b1fe654e0bf1077b8e7ce62e762526997d3bf6643183 +size 26658 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b1c46564b6491b0e6b3b6b5cff3e22171acb7d3 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bec1a75987d82225f2e8d9a3c652c4c9da15c32b6333f1bb2e9423334f5b62d +size 43616 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/a97f7c055c1fd8d79037d02b3fc38496_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/a97f7c055c1fd8d79037d02b3fc38496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f60709dacc04937d335e944420a79663f45bd50f --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/a97f7c055c1fd8d79037d02b3fc38496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8c9a72a87d6a7c9edac3c396a6e71b215ab24ebfbfd5f26e0bee69f47d93364 +size 10846 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a00400b9b98eb1d7238f9c786aea6f824734ced --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9773beae025c2441fe6cd4e98cdcee3c9ffad2dcb3c7c6a9348f1940a274471d +size 19940 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dfa001d050552c02a052cddc8325b238826a5b5 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:330d615b0627be5f8b8463a8a0b4dfb3cdd8208f2b261ab215183eeca382d0cf +size 153815 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/b385e39c8b32616bd23ad744a3f71cfa_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/b385e39c8b32616bd23ad744a3f71cfa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67b34039f618812556e4e1cb57ecfa9301a30401 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/b385e39c8b32616bd23ad744a3f71cfa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2beb4e6e70e960fc0dc1f962028c991ac169613c7279fa3a33460f172284ca1f +size 10563 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/bd50d56ae2c12a92466ba2aea1a78040_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/bd50d56ae2c12a92466ba2aea1a78040_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da616dc92a97872b6cbe13cc83d0972a957157f9 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/bd50d56ae2c12a92466ba2aea1a78040_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f25db3eca168d13d55cf0e45815b0d5f21aa4dce84f9eb72e36133cec4597c61 +size 49102 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f9251398e7b3f175b5a356ea8e0ad21dddb9124 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9e262d3c28ff0031306eef088b40f077f7caf9f33593be556815bd79412e54f +size 10006 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c0c7f65c51c83fbe595b47326f6b089a_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c0c7f65c51c83fbe595b47326f6b089a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52b825b1025512cbd99c13cda13e5569934675bf --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c0c7f65c51c83fbe595b47326f6b089a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f818fcef95e03315027aed181233816fd2e90fba0d365a67f016435ccff4e509 +size 24230 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c0f64806753a053854921deb8f4fc798_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c0f64806753a053854921deb8f4fc798_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d518bb112a39731fd3a85fd55324787862e3a166 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c0f64806753a053854921deb8f4fc798_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56d612846c01790ed0f07e0602c62080e2e4a83ccb466d9862414c85394014db +size 11913 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00d33c0f3a15659da550c977fe203d4ab732795d --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:421be8754c1fab38609cabad8944b8991e93962f360714aa58e63e97120bf8b4 +size 28555 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acd369ca9348cd29745d52fa6f90a2471c9bcad4 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf9c869dd51cb32dbbe5111db3deb2e8d641e8464e99440d9438890aef441849 +size 56442 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..644e1576a023755bd790c078682683b76188c76c --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:471d9811bbf004e2abcbd3a4861b7ec429578fedf9c57c34fca488cf299262ad +size 58849 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29864c18429d469afb818090f5aefb6728aca059 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3014fbe98ca8cb60e65690a62600a761704657cbe4123fb5c0108c557fd02f9d +size 26055 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c29442c8ba87e2e099594d4f5bde3b7ad6037c7 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62ca3c327a7c57e7a9285489f4b0a9a0f0fc83497b1002c300cfcaf2e498f3d9 +size 122017 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ac19ad4b65a3aea0f18c0c28225a091f1370285 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:296d0a580fccc5b9e2cdc068656070206b3140b11a499ec61e2bb5a516b66fe8 +size 17000 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58bf2fbc1a48c64f0e5bb5bc0e86649f5c105f01 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1deb93a6f19e3944dfe58e0c772420a3526c683256cc82e5ab70a1ec7cecf0be +size 21514 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d023a7c4497d48944e3218715552572798b45a5 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d4214c790caa32a4903d52257b4694addcc6567d1a5d453842b41af0f0495b1 +size 18102 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf7f9ab082bbbce50c67814b4eb2420e87d180c2 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:518714b1c7089366127ca5dadb89fd5bbcaa20aba7daacff3e51956db7437f41 +size 47033 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/dbfe5a97dc7e71fd9ae813d4bb865e29_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/dbfe5a97dc7e71fd9ae813d4bb865e29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b04e53d6604839d17eefb07d1ad67d112fbc6fa --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/dbfe5a97dc7e71fd9ae813d4bb865e29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58c7e1bf532b9112741f75c4239aa5a527e3982a9fdcf8acd0eb32ebb0163f93 +size 13356 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b497d7655c650bc7f7ba8ac51ad0762d911bdd2 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:575a4701fa98c5be3035186914c514d590fd4bb13a6376506111e346da4b2bd6 +size 41439 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbc16c6b8878cc5a332a2c0b96979878bc626164 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b1f50babc279d4147b42d1457bf7b580a8e707a80cab7f19912cc670f9790b2 +size 136723 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ac8bd4dc8acd1ff9b107d1266e845dc3c4d9fc8 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24b72fe93f6fdb28749409356ac5bdd6e3f92b41bf6505e83106b37bfcc28a44 +size 25132 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..910b537b79077b2438105c177d5038b3b0586130 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd5d921c203c1170b473713e98477caf827fcef25aa2dd1ad8516360dcc63b74 +size 96472 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b216ab79306d1f3dbb5b4adf5a579471dbfb164 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdcde627ca1424a6f9253b42575cbda6b9af79057f31e96e32b7893c1044162d +size 21907 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cf69c39d7e2425827ca743c6ea17dfbf4134309 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29339008c2d56d5fd81e1e9789b6f30ea4f555bce9486f54bc86345ce1ecd6da +size 113378 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62bbab3b9722838f9db1b054912db9ad81908ef8 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1be2440ac5a455d5d66cc9d1b59acd3ce0d875c0f429888c6f47316d8e3d695b +size 28759 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07c5a76666f298c740a153b52bb950a89ca581a8 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b684b063cca70631a92d72260b438c86786a1b175c4ed68b9fc2e3ef64b4e5ab +size 10981 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f8f8916ae391a1233c13ce738c699109_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f8f8916ae391a1233c13ce738c699109_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9855df816c9ad50bfa4c871032957350473450e5 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f8f8916ae391a1233c13ce738c699109_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ac3c4d04df70124c03f86298124e1f93636f81b109f8a0ac2860c2df6955a8f +size 180165 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfed5936a0a0d07dc7f47a8950006b29a5cb33f1 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcb7cf67fd7cb3c55c374732ca7e5ed5379b29ca5c1f160ed0c878848454e684 +size 53067 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd26c7a6fad1ab512de45a806e9daed2a8b8939b --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebf9ca3ccb5e203022957911dc68e0686c7d5081a7049569d40f446b38039988 +size 34560 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f06768d8879dfa4f0555f9447bd16c82d7d47f2a --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:494f7df493528a011505407b147f5511a776909cb659f825b569b93d673b5cb7 +size 117226 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd9f29a59926f4f268124da556474938446a0ac6 --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61bdc79f33acc46c8bf41f720b9ec29a7500883e31ab9cbb078762cf8dc3924e +size 26801 diff --git a/marked/G/T-REC-G.8121.1-201811-I_PDF-E/raw.md b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..076c5e0230b05d4ef395d4051f79a7a19094560a --- /dev/null +++ b/marked/G/T-REC-G.8121.1-201811-I_PDF-E/raw.md @@ -0,0 +1,3081 @@ + + +# ITU-T G.812.1/Y.1381.1 + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(11/2018) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Packet over Transport aspects – MPLS over Transport +aspects + +SERIES Y: GLOBAL INFORMATION +INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, +NEXT-GENERATION NETWORKS, INTERNET OF +THINGS AND SMART CITIES + +Internet protocol aspects – Transport + +--- + +**Characteristics of MPLS-TP equipment +functional blocks supporting +ITU-T G.813.1/Y.1372.1 OAM mechanisms** + +Recommendation ITU-T G.812.1/Y.1381.1 + +## 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 | +| PACKET OVER TRANSPORT ASPECTS | G.8000–G.8999 | +| Ethernet over Transport aspects | G.8000–G.8099 | +| MPLS over Transport aspects | G.8100–G.8199 | +| Synchronization, quality and availability targets | G.8200–G.8299 | +| Service Management | G.8600–G.8699 | +| ACCESS NETWORKS | G.9000–G.9999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T G.8121.1/Y.1381.1 + +# Characteristics of MPLS-TP equipment functional blocks supporting ITU-T G.8113.1/Y.1372.1 OAM mechanisms + +# Summary + +Recommendation ITU-T G.8121.1/Y.1381.1 specifies both the functional components and the methodology that should be used in order to specify multi-protocol label switching – transport profile (MPLS-TP) layer network functionality of network elements based on the protocol neutral constructs defined in Recommendation ITU-T G.8121 and on the tools defined in Recommendation ITU-T G.8113.1/Y.1372.1. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|---------------------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.8121.1/Y.1381.1 | 2013-11-06 | 15 | 11.1002/1000/12019 | +| 2.0 | ITU-T G.8121.1/Y.1381.1 | 2016-04-13 | 15 | 11.1002/1000/12805 | +| 2.1 | ITU-T G.8121.1/Y.1381.1 (2016) Cor. 1 | 2016-11-13 | 15 | 11.1002/1000/13101 | +| 3.0 | ITU-T G.8121.1/Y.1381.1 | 2018-11-29 | 15 | 11.1002/1000/13760 | + +# Keywords + +Atomic functions, equipment functional blocks, MPLS-TP layer network, MPLS-TP, OAM, PTN. + +--- + +\* To access the Recommendation, type the URL
TxFCb = TxFC[p]"]; D --> E[/LMRo.D(OAM),
LMRo.CoS(CoS),
LMRo.DP(DP)/]; E --> B; +``` + +G.8121.1-Y.1381.1(18)\_F8-33 + +Flowchart of the LMRo Generation process. The steps are: LMRo Generation (oval), Waiting (oval), RI\_LMMo(OAM, CoS, DP) (parallelogram), OPC(OAM)=LMRo, TxFCb = TxFC[p] (rectangle), and LMRo.D(OAM), LMRo.CoS(CoS), LMRo.DP(DP) (parallelogram). A feedback loop connects the final output back to the Waiting state. + +Figure 8-33 – LMR generation behaviour + +Upon receipt of RI containing an LMMo traffic unit, the LMRo generation process generates a DMR traffic unit and forwards it to the OAM insertion process. + +As part of the DMR generation: + +- the Opcode is changed into DMRo Opcode; +- the TxFCb field is assigned the value of the Tx counter; +- all the other fields are copied from the RI containing the original DMMo traffic unit. + +#### 8.8.5.6 On-demand LMR Reception process + +The on-demand LMR Reception process that is in the on-demand LMRo Sink control process processes the received LMRo traffic units and the complementing CoS and DP signals. The behaviour is defined in Figure 8-34. + +![Flowchart of LMR reception behaviour. The process starts with 'LMRo Reception' (oval), followed by 'Waiting' (oval), then a parallelogram containing 'LMRo.D(OAM), LMRo.CoS(CoS), LMRo.DP(DP)'. This leads to a parallelogram containing 'RI_LMR( TxFCf(OAM), RxFCf(OAM), TxFCb(OAM), RxFC[p] )'. A feedback loop arrow goes from the bottom parallelogram back to the 'Waiting' oval. The diagram is labeled G.8121.1-Y.1381.1(18)_F8-34.](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +``` + +graph TD + A([LMRo Reception]) --> B([Waiting]) + B --> C[/LMRo.D(OAM), LMRo.CoS(CoS), LMRo.DP(DP)/] + C --> D[/RI_LMR( TxFCf(OAM), RxFCf(OAM), TxFCb(OAM), RxFC[p] )/] + D --> B + style A fill:none,stroke:none + style B fill:none,stroke:none + style C fill:none,stroke:none + style D fill:none,stroke:none + +``` + +G.8121.1-Y.1381.1(18)\_F8-34 + +Flowchart of LMR reception behaviour. The process starts with 'LMRo Reception' (oval), followed by 'Waiting' (oval), then a parallelogram containing 'LMRo.D(OAM), LMRo.CoS(CoS), LMRo.DP(DP)'. This leads to a parallelogram containing 'RI\_LMR( TxFCf(OAM), RxFCf(OAM), TxFCb(OAM), RxFC[p] )'. A feedback loop arrow goes from the bottom parallelogram back to the 'Waiting' oval. The diagram is labeled G.8121.1-Y.1381.1(18)\_F8-34. + +**Figure 8-34 – LMR reception behaviour** + +#### 8.8.5.7 Counter process for Single-ended on-demand Packet Loss Measurement + +This process counts the number of transmitted and received packets. + +This counter process counts exactly the same packets as the counter process defined in clause 8.8.4.7. + +### 8.8.6 Proactive packet delay measurement (DMp) + +#### 8.8.6.1 Overview + +To support this functionality, proactive delay measurement (DM) as described in clause 8.2.8 of [ITU-T G.8113.1] for single-ended DM and clause 8.2.7 of [ITU-T G.8113.1] for dual-ended DM is used. + +Figure 8-35 provides the different processes inside MEPs and MIPs that are involved in the single-ended Delay Measurement Protocol. + +The MEP proactive OAM insertion process is defined in clause 9.2.1.1, the MEP OAM proactive extraction process in clause 9.2.1.2. In summary, these processes insert and extract MT\_CI OAM signals into and from the stream of MT\_CI\_D traffic units and the complementing CoS and D signals going through an MEP and MIP; the extraction is based on the OAM\_Tool. + + + +G.8121.1-Y.1381.1(18)\_F8-35 + +Figure 8-35: Overview of processes involved with proactive single-ended delay measurement. The diagram shows three vertical blocks representing network elements. The left block (MEP) contains G-ACh insertion, OAM PDU generation, DMMp source control, DMRp sink control, OAM PDU reception, and G-ACh extraction. The middle block contains two 'On-demand MIP' units. The right block (MIP) contains G-ACh extraction, OAM PDU reception, DMMp sink control, DMRp source control, OAM PDU generation, and G-ACh extraction. Various management interfaces (MT\_CI, MI\_GAL\_Enable, MI\_TTLVALUE, MI\_DMp\_OAM\_Tool, etc.) are shown connected to the processes. A return path for RI\_DMRp messages is also depicted. + +**Figure 8-35 – Overview of processes involved with proactive single-ended delay measurement** + +The proactive DM control process controls the proactive DM protocol. If MI\_DMp\_Enable is set, the DMM packets are sent periodically. The DMM packets are generated with a periodicity determined by MI\_DMp\_Period and with a priority determined by MI\_DMp\_CoS. The result (B\_FD, F\_FD, N\_FD) is reported via a DMRp Sink Control process. If the proactive DM control process activates multiple monitoring on different CoS levels simultaneously, each result is independently managed per CoS level. Optional test ID TLVs can be utilized to distinguish each measurement, if multiple measurements are simultaneously activated in an ME. + +Figure 8-36 provides the different processes inside MEPs and MIPs that are involved with proactive dual-ended DM. + + + +G.8121.1-Y.1381.1(18)\_F8-36 + +Figure 8-36: Overview of processes involved with proactive dual-ended delay measurement. The diagram shows three vertical blocks. The left block (MEP) contains G-ACh insertion, OAM PDU generation, and IDMp source control. The middle block contains an 'On-demand MIP' unit. The right block (MIP) contains G-ACh extraction, OAM PDU reception, IDMp sink control, and Performance monitoring. Management interfaces (MT\_CI, MI\_GAL\_Enable, MI\_TTLVALUE, MI\_IDMp\_OAM\_Tool, etc.) are connected to the processes. The Performance monitoring process outputs MI\_pN\_FD. + +**Figure 8-36 – Overview of processes involved with proactive dual-ended delay measurement** + +The MEP proactive-OAM source insertion process is defined in clause 9.2.1.1, the MEP proactive OAM sink extraction process in clause 9.2.1.2 and the MIP on-demand OAM sink extraction process in clause 9.4.2.2. + +The 1DMp Source Control process triggers the generation of 1DMp traffic units if MI\_1DM\_Enable signal is set. The 1DM packets are generated with a periodicity determined by MI\_1DMp\_Period and with a priority determined by MI\_1DMp\_CoS. The result (N\_FD) is reported via 1DMp Sink Control process. + +#### **8.8.6.2 Proactive DM Source Control process** + +The behaviour of the proactive DM control process is defined in Figure 8-37. If the MI\_DMp\_Enable is asserted, the process starts to generate DMM packets (using the DMM(MI\_DM\_CoS,1, Test ID TLV,TLV) signal). The result (B\_FD, F\_FD, N\_FD) is reported via a DMR reception. + + + +``` + +graph TD + Start([Proactive DM control]) --> Disabled([Disabled]) + Disabled --> MI_DMp_Enable{{MI_DMp_Enable}} + MI_DMp_Enable --> Set0Timer[Set(0, Timer)] + Set0Timer --> Enabled([Enabled]) + Enabled --> Timer{{Timer}} + Enabled --> RI_DMR[RI_DMR(TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, rTestID)] + Enabled --> NotMI_DMp_Enable{{!MI_DM_Enable}} + Timer --> TestIDTLV[Test ID TLV = GenID ( MI_DMp_Test ID )] + TestIDTLV --> TLV[TLV = Generate( MI_DMp_Length )] + TLV --> DMM[DMM(MI_DM_CoS, 1, Test ID TVL, )] + DMM --> SetPeriodTimer[Set(MI_DMp_Period, Timer)] + SetPeriodTimer --> DM_Result[DM_Result(B_FD, F_FD, N_FD)] + RI_DMR --> DecisionMI_DM_TestID{MI_DM_TestID!=NULL and rTestID!=MI_DMp_TestID} + DecisionMI_DM_TestID -- Y --> InvalidF[ F_FD = Invalid +N_FD = Invalid ] + DecisionMI_DM_TestID -- N --> B_FD[B_FD = (RxTimeb - TxTimeStampf) +- (TxTimeStampb - RxTimeStampf)] + B_FD --> DecisionTxTimeStamp{TxTimeStampb = RxTimeStampf = 0?} + DecisionTxTimeStamp -- N --> InvalidF + DecisionTxTimeStamp -- Y --> ValidF[ F_FD = RxTimeStampf - TxTimeStampf +N_FD = RxTimeb - TxTimeStampb ] + InvalidF --> DM_Result + ValidF --> DM_Result + +``` + +Flowchart of Proactive DM control behaviour. The process starts with 'Proactive DM control' leading to 'Disabled', then 'MI\_DMp\_Enable', and 'Set(0, Timer)'. It then enters an 'Enabled' state. From 'Enabled', it branches into 'Timer', 'RI\_DMR(...)', and '!MI\_DM\_Enable'. The 'Timer' path leads to 'Test ID TLV = GenID ( MI\_DMp\_Test ID )', 'TLV = Generate( MI\_DMp\_Length )', 'DMM(MI\_DM\_CoS, 1, Test ID TVL, )', and 'Set(MI\_DMp\_Period, Timer)'. The 'RI\_DMR(...)' path leads to a decision 'MI\_DM\_TestID!=NULL and rTestID!=MI\_DMp\_TestID'. If 'Y', it leads to 'F\_FD = Invalid' and 'N\_FD = Invalid'. If 'N', it leads to 'B\_FD = (RxTimeb - TxTimeStampf) - (TxTimeStampb - RxTimeStampf)'. From 'B\_FD', it leads to a decision 'TxTimeStampb = RxTimeStampf = 0?'. If 'N', it leads to 'F\_FD = Invalid' and 'N\_FD = Invalid'. If 'Y', it leads to 'F\_FD = RxTimeStampf - TxTimeStampf' and 'N\_FD = RxTimeb - TxTimeStampb'. All paths lead to 'DM\_Result(B\_FD, F\_FD, N\_FD)'. + +G.8121.1-Y.1381.1(18)\_F8-37 + +Figure 8-37 – Proactive DM control behaviour + +#### 8.8.6.3 Proactive DMM Generation process + +The behaviour of the DMMp generation process that is in the DMM Source control process is defined in Figure 8-38. + + + +``` +graph TD; A([DMMp Generation]) --> B([Waiting]); B --> C[/DMMp(CoS, Test ID TLV)/]; C --> D[OAM=DMMp(CoS, Test ID TLV)]; D --> E[TxTimeStamp(OAM)=Local Time]; E --> F[/D(OAM, CoS(CoS), DP(0))/]; F --> A; +``` + +The flowchart illustrates the DMMp Generation process. It begins with a rounded rectangle labeled 'DMMp Generation', which points down to another rounded rectangle labeled 'Waiting'. From 'Waiting', the flow proceeds down to a chevron-shaped box labeled 'DMMp(CoS, Test ID TLV)'. This is followed by a rectangular box labeled 'OAM=DMMp(CoS, Test ID TLV)'. Next is a rectangular box labeled 'TxTimeStamp(OAM)=Local Time'. The final step is a chevron-shaped box labeled 'D(OAM, CoS(CoS), DP(0))'. A blue arrow loops back from the bottom of the final chevron to the top of the 'Waiting' box. Below the flowchart, the text 'G.8121.1-Y.1381.1(18)\_F8-38' is displayed. + +Flowchart of the DMMp Generation process + +**Figure 8-38 – DMM generation behaviour** + +Upon receiving the DMM(CoS, Test ID TLV), a single DMM traffic unit is generated together with the complementing CoS and DP signals. The TxTimeStamp field is assigned the value of the local time. + +The CoS signal value is defined by DMM(CoS). The DP signal is set to 0. The test ID signal is determined by the DMM(Test ID TLV) signal. + +#### 8.8.6.4 Proactive DMM Reception process + +The proactive DMM reception process that is in the proactive DMM Sink control process processes the received proactive DMM traffic units and the complementing CoS and DP signals. The behaviour is defined in Figure 8-39. + + + +``` +graph TD; A([DMMp Reception]) --> B[/Waiting/]; B --> C[/D(OAM), CoS(CoS), DP(DP)/]; C --> D[RxTimeStampf(OAM)= Local_Time]; D --> E[/RI_DMMp(OAM, CoS, DP)/]; E --> B; +``` + +The flowchart illustrates the DMM reception process. It begins with 'DMMp Reception' (oval), followed by 'Waiting' (oval), then 'D(OAM), CoS(CoS), DP(DP)' (parallelogram), 'RxTimeStampf(OAM)= Local\_Time' (rectangle), and 'RI\_DMMp(OAM, CoS, DP)' (parallelogram). A feedback loop connects the final step back to the 'Waiting' state. The diagram is labeled G.8121.1-Y.1381.1(18)\_F8-39. + +Flowchart of DMM reception behaviour + +Figure 8-39 – DMM reception behaviour + +traffic unit and the complementing CoS and DP signals are forwarded as RI to the DMR Generation process. + +#### 8.8.6.5 Proactive DMR Generation process + +The Proactive DMR Generation process that is in the DMR Source control process generates a DMRp traffic unit and its complementing CoS and DP signals. The behaviour is defined in Figure 8-40. + + + +``` +graph TD; A([DMRp Generation]) --> B[/Waiting/]; B --> C[/RI_DMMp(OAM, CoS, DP)/]; C --> D[OPC(OAM)=DMRp +TxTimeStampb(OAM) = Local Time]; D --> E[/D(OAM), D.CoS(CoS), D.DP(DP)/]; E --> B; +``` + +The flowchart illustrates the Proactive DMR Generation process. It starts with 'DMRp Generation' (oval), followed by 'Waiting' (oval), then 'RI\_DMMp(OAM, CoS, DP)' (parallelogram), 'OPC(OAM)=DMRp TxTimeStampb(OAM) = Local Time' (rectangle), and 'D(OAM), D.CoS(CoS), D.DP(DP)' (parallelogram). A feedback loop connects the final step back to the 'Waiting' state. The diagram is labeled G.8121.1-Y.1381.1(18)\_F8-40. + +Flowchart of Proactive DMR Generation behaviour + +Figure 8-40 – Proactive DMR Generation behaviour + +Upon the receipt of RI containing a DMMp traffic unit, the DMR generation process generates a DMR traffic unit and forwards it to the OAM Insertion process. + +As part of the DMR generation: + +- the Opcode is changed into DMRp Opcode; +- the TxTimeStampb field is assigned the value of the Local Time; +- all the other fields (including TLVs and padding after the End TLV) are copied from the RI containing the original DMM traffic unit. + +The TLVs are copied from the RI containing the original DMM traffic unit. If multiple TLVs exist, the order of the TLVs is unchanged. + +#### 8.8.6.6 Proactive DMR Reception process + +The proactive DMR Reception process that is in the DMRp Sink control process processes the received DMRp traffic units and the complementing CoS and DP signals. The behaviour is defined in Figure 8-41. + + + +``` +graph TD; A([DMRp Reception]) --> B([Waiting]); B --> C[/D(OAM), CoS(CoS), DP(DP)/]; C --> D[/RI_DMRp(TxTimeStampf(OAM), RxTimeStampf(OAM), TxTimeStampb(OAM), Local Time)/]; D --> A; +``` + +The flowchart illustrates the DMR Reception behaviour. It begins with a rounded rectangle labeled 'DMRp Reception', which points down to another rounded rectangle labeled 'Waiting'. From 'Waiting', the flow proceeds down to a chevron-shaped box containing 'D(OAM), CoS(CoS), DP(DP)'. Below this is another chevron-shaped box containing 'RI\_DMRp(TxTimeStampf(OAM), RxTimeStampf(OAM), TxTimeStampb(OAM), Local Time)'. A feedback loop is shown by a blue line originating from the bottom of the final chevron and pointing back up to the 'Waiting' box. The diagram is labeled with the code 'G.8121.1-Y.1381.1(18)\_F8-41' at the bottom right. + +Flowchart of DMR Reception behaviour + +Figure 8-41 – DMR Reception behaviour + +If the DMR traffic unit is processed, the TxTimeStampf, RxTimeStampf, TxTimeStampb and Test ID are extracted from the traffic unit and signalled together with the Local Time. + +#### 8.8.6.7 Proactive 1DM Source Control process + +The behaviour of the proactive 1DM control process is defined in Figure 8-42. + +If the MI\_1DMp\_Enable is asserted, the process starts to generate 1DMp packets (using the 1DMp(MI\_1DMp\_CoS, Test ID TLV) signal). + + + +``` + +graph TD + A([IDMp Control So]) --> B([Disabled]) + B --> C[/MI_1DMp_Enable/] + C --> D[Set(0, Timer)] + D --> E([Enabled]) + E --> F[/Timer/] + E --> G[/!MI_1DMp_Enable/] + F --> H[Test ID TLV = GenID ( MI_1DMp_Test ID )] + H --> I[TLV = Generate( MI_1DMp_Length )] + I --> J[/IDMp(MI_1DM_Pri, Test ID TVL)/] + J --> K[Set(MI_1DMp_Period, Timer)] + K --> A + G --> A + +``` + +G.8121.1-Y.1381.1(18)\_F8-42 + +Flowchart of Proactive 1DM Control\_So behaviour. The process starts with 'IDMp Control So' (oval), leading to 'Disabled' (oval), then 'MI\_1DMp\_Enable' (parallelogram), then 'Set(0, Timer)' (rectangle). It then reaches 'Enabled' (oval). From 'Enabled', it branches into 'Timer' (parallelogram) and '!'MI\_1DMp\_Enable' (parallelogram). The 'Timer' path leads to 'Test ID TLV = GenID ( MI\_1DMp\_Test ID )' (rectangle), then 'TLV = Generate( MI\_1DMp\_Length )' (rectangle), then 'IDMp(MI\_1DM\_Pri, Test ID TVL)' (parallelogram), and finally 'Set(MI\_1DMp\_Period, Timer)' (rectangle). A feedback loop from 'Set(MI\_1DMp\_Period, Timer)' returns to the entry point between 'IDMp Control So' and 'Disabled'. A feedback loop from '!'MI\_1DMp\_Enable' also returns to the entry point between 'IDMp Control So' and 'Disabled'. + +**Figure 8-42 – Proactive 1DM Control\_So behaviour** + +#### 8.8.6.8 Proactive 1DM Generation process + +Figure 8-43 shows the proactive 1DM Generation process in the 1DM Source control process. Upon receiving the IDMp(CoS) signal, a single 1DM traffic unit is generated by the OAM=1DM (CoS, LocalTime) call. + +Together with this IDMp traffic unit, the complementing CoS and DP signals are generated. The TxTimeStampf field is assigned the value of the Local Time. The value of the CoS signal is determined by the IDMp(CoS) signal. The DP signal is set to 0. + + + +``` + +graph TD + A([1DMp Generation]) --> B([Waiting]) + B --> C[/1DMp(CoS)/] + C --> D[OAM=1DMp(CoS, LocalTime,)] + D --> E[/D(OAM, CoS(CoS), DP(0))/] + E --> B + +``` + +G.8121.1-Y.1381.1(18)\_F8-43 + +Flowchart of 1DM Generation behaviour. The process starts with '1DMp Generation' (oval), followed by 'Waiting' (oval), then '1DMp(CoS)' (parallelogram), then 'OAM=1DMp(CoS, LocalTime,)' (rectangle), and finally 'D(OAM, CoS(CoS), DP(0))' (parallelogram). A feedback loop connects the final step back to the 'Waiting' step. The diagram is labeled G.8121.1-Y.1381.1(18)\_F8-43. + +**Figure 8-43 – 1DM Generation behaviour** + +#### 8.8.6.9 Proactive 1DM Reception process + +The proactive 1DM Reception process in the 1DM Sink control process processes the received 1DMp traffic units and the complementing P and CoS signals. The behaviour is defined in Figure 8-44. + + + +``` + +graph TD + A([1DMp Reception]) --> B([Waiting]) + B --> C[/D(OAM, CoS(CoS), DP(DP))/] + C --> D[/1DMp(TxTimeStampf(OAM), Local Time)/] + D --> B + +``` + +G.8121.1-Y.1381.1(18)\_F8-44 + +Flowchart of 1DM Reception behaviour. The process starts with '1DMp Reception' (oval), followed by 'Waiting' (oval), then 'D(OAM, CoS(CoS), DP(DP))' (parallelogram), and finally '1DMp(TxTimeStampf(OAM), Local Time)' (parallelogram). A feedback loop connects the final step back to the 'Waiting' step. The diagram is labeled G.8121.1-Y.1381.1(18)\_F8-44. + +**Figure 8-44 – 1DM Reception behaviour** + +If the 1DMp traffic unit is processed, the TxTimeStampf fields are extracted and forwarded to the 1DMp Control\_Sk process together with the Local Time using the 1DMp (TxTimeStampf, RxTimef) signal. + +#### 8.8.6.10 Proactive 1DM Sink Control\_Sk process + +The behaviour of the proactive 1DMp Control Sink process is defined in Figure 8-45. If the MI\_1DMp\_Enable is asserted, the result (N\_FD) is reported via a 1DMp reception. + + + +``` + +graph TD + A([IDMp Control Sk]) --> B([Disabled]) + B --> C[/MI_1DMp_Enable/] + C --> D([Enabled]) + D --> E[/IDMp(rCoS, TxTimeStampf, RxTimef, rTestID)/] + D --> F[/!MI_1DMp_Enable/] + E --> G{rCoS= MI_1DM_CoS?} + F --> G + G -- N --> D + G -- Y --> H{MI_1DMp_TestID!=NULL and rTestID!=MI_1DMp_TestID} + H -- Y --> D + H -- N --> I[N_FD = RxTimef - TxTimeStampf] + I --> J[IDM_Result(N_FD)] + J --> D + +``` + +G.8121.1-Y.1381.1(18)\_F8-45 + +Flowchart of the Proactive 1DM Control Sink process. The process starts with 'IDMp Control Sk' (oval), leading to 'Disabled' (oval), then 'MI\_1DMp\_Enable' (parallelogram), then 'Enabled' (oval). From 'Enabled', it branches to 'IDMp(rCoS, TxTimeStampf, RxTimef, rTestID)' (parallelogram) and '!MI\_1DMp\_Enable' (parallelogram). Both lead to a decision diamond 'rCoS= MI\_1DM\_CoS?'. If 'N' (No), it loops back to 'Enabled'. If 'Y' (Yes), it leads to another decision diamond 'MI\_1DMp\_TestID!=NULL and rTestID!=MI\_1DMp\_TestID'. If 'Y' (Yes), it loops back to 'Enabled'. If 'N' (No), it leads to 'N\_FD = RxTimef - TxTimeStampf' (rectangle), then 'IDM\_Result(N\_FD)' (rectangle), which then loops back to 'Enabled'. + +**Figure 8-45 – Proactive 1DM Control Sink process** + +### 8.8.7 On-demand packet delay measurement (DMo) + +#### 8.8.7.1 Overview + +To support this functionality, on-demand Delay Measurement (DMM/DMR) as described in clause 8.2.7 of [ITU-T G.8113.1] for dual-ended and clause 8.2.8 of [ITU-T G.8113.1] for single-ended is used. + +Figure 8-46 provides the different processes inside MEPs and MIPs that are involved in the single-ended Delay Measurement Protocol. + +The MEP On-Demand-OAM Source insertion process is defined in clause 9.4.1.1, the MEP On-Demand OAM Sink Extraction process in clause 9.4.1.2, the MIP On-Demand OAM Source Insertion process in clause 9.4.2.1.1 and the MIP On-Demand OAM Sink Extraction process in clause 9.4.2.1.2. In summary, these processes insert and extract MT\_CI OAM signals into and from the stream of MT\_C\_D traffic units and the complementing PHB signals going through an MEP and MIP. + + + +G.8121.1-Y.1381.1(18)\_F8-46 + +Figure 8-46: Overview of processes involved with on-demand Delay Measurement. The diagram shows two Main Terminal (MT) units connected via an On-demand MIP. The left MT contains a G-ACh insertion block, an OAM PDU generation block, a DMMo source control block, a DMRo sink control block, an OAM PDU reception block, and a G-ACh extraction block. The right MT contains a G-ACh extraction block, an OAM PDU reception block, a DMMo sink control block, a DMRo source control block, an OAM PDU generation block, and a G-ACh extraction block. Various management interfaces (MT\_CI, MI\_GAL\_Enable, MI\_TTLVALUE, MI\_DMo\_Start, MI\_DMo\_OAM\_Tool, MI\_DMo\_Terminate, MI\_DMo\_CoS, MI\_DMo\_Result, RI\_DMRo, RI\_DMMo) are shown interacting with these blocks. A central dashed box represents the On-demand MIP. + +**Figure 8-46 – Overview of processes involved with on-demand Delay Measurement** + +The DMMo source control process controls the DM protocol. The protocol is activated upon receipt of the MI\_DMo\_Start(CoS,Period) signal and remains activated until the MI\_DMo\_Terminate signal is received. The result is communicated via the MI\_DMo\_Result(count, B\_FD[], F\_FD[], N\_FD[]) signal. + +The DMMo source control process generates DMMo traffic units that pass through MIPs transparently, but are received and processed by DMMo sink control processes in MEPs. The DMRo source control process may generate a DMRo traffic unit in response. This DMRo traffic unit also passes transparently through MIPs, but is received and processed by DMRo sink control processes in MEPs. + +On the Source MEP side, the DMMo source control process stamps the value of the Local Time to the TxTimeStampf field in the DMMo message when the first bit of the packet is transmitted. Note that on the sink MEP side, the DMMo sink control process stamps the value of the Local Time to the RxTimeStampf field in the DMMo message when the last bit of the packet is received. + +The DMRo source and sink control process stamps with the same way as the DMMo source and sink control process. + +Figure 8-47 provides the different processes inside MEPs and MIPs that are involved in the dual-ended Delay Measurement Protocol. + +The MEP On-Demand OAM Source insertion process is defined in clause 9.2, the MEP On-Demand-OAM Sink extraction process in clause 9.2, the MIP On-Demand OAM Sink Extraction process in clause 9.4 and the MIP On-Demand OAM Source insertion process in clause 9.4. In summary, these processes insert and extract MT\_CI OAM signals into and from the stream of MT\_CI\_D traffic units and the complementing PHB signals going through an MEP and MIP. + +![Figure 8-47: Overview of processes involved with on-demand one way delay measurement. The diagram shows three main components: a Source MEP, an On-demand MIP, and a Sink MEP. The Source MEP contains three stacked boxes: 'G-ACh insertion', 'OAM PDU generation', and '1DMo source control'. Inputs to 'G-ACh insertion' are 'MT_CI' and 'MI_GAL_Enable'. Inputs to 'OAM PDU generation' are 'MI_TTLVALUE'. Inputs to '1DMo source control' are 'MI_1DMo_Start (CoS, Period)', 'MI_1DMo_OAM_Tool', 'MI_1DMo_Terminate', and 'MI_1DMo_CoS'. Arrows show data flow from '1DMo source control' up to 'OAM PDU generation' and then to 'G-ACh insertion'. An arrow from 'G-ACh insertion' points to the 'On-demand MIP' (a dashed box). An arrow from the 'On-demand MIP' points to the 'Sink MEP'. The Sink MEP contains three stacked boxes: 'G-ACh extraction', 'OAM PDU reception', and '1DMo sink control'. Arrows show data flow from 'G-ACh extraction' down to 'OAM PDU reception' and then to '1DMo sink control'. Inputs to 'G-ACh extraction' are 'MT_CI' and 'MI_GAL_Enable'. Inputs to '1DMo sink control' are 'MI_1DMo_OAM_Tool', 'MI_1DMo_Start(CoS)', and 'MI_1DMo_Terminate'. An output from '1DMo sink control' is 'MI_1DMo_Result (count, N_FD[])'. A reference code 'G.8121.1-Y.1381.1(18)_F8-47' is at the bottom right.](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +Figure 8-47: Overview of processes involved with on-demand one way delay measurement. The diagram shows three main components: a Source MEP, an On-demand MIP, and a Sink MEP. The Source MEP contains three stacked boxes: 'G-ACh insertion', 'OAM PDU generation', and '1DMo source control'. Inputs to 'G-ACh insertion' are 'MT\_CI' and 'MI\_GAL\_Enable'. Inputs to 'OAM PDU generation' are 'MI\_TTLVALUE'. Inputs to '1DMo source control' are 'MI\_1DMo\_Start (CoS, Period)', 'MI\_1DMo\_OAM\_Tool', 'MI\_1DMo\_Terminate', and 'MI\_1DMo\_CoS'. Arrows show data flow from '1DMo source control' up to 'OAM PDU generation' and then to 'G-ACh insertion'. An arrow from 'G-ACh insertion' points to the 'On-demand MIP' (a dashed box). An arrow from the 'On-demand MIP' points to the 'Sink MEP'. The Sink MEP contains three stacked boxes: 'G-ACh extraction', 'OAM PDU reception', and '1DMo sink control'. Arrows show data flow from 'G-ACh extraction' down to 'OAM PDU reception' and then to '1DMo sink control'. Inputs to 'G-ACh extraction' are 'MT\_CI' and 'MI\_GAL\_Enable'. Inputs to '1DMo sink control' are 'MI\_1DMo\_OAM\_Tool', 'MI\_1DMo\_Start(CoS)', and 'MI\_1DMo\_Terminate'. An output from '1DMo sink control' is 'MI\_1DMo\_Result (count, N\_FD[])'. A reference code 'G.8121.1-Y.1381.1(18)\_F8-47' is at the bottom right. + +**Figure 8-47 – Overview of processes involved with on-demand one way delay measurement** + +The 1DM protocol is controlled by the 1DM Source Control and 1DM Sink Control processes. The 1DM Source Control process triggers the generation of 1DM traffic units upon the receipt of an MI\_1DM\_Start(iPHB, oPHB, Period) signal. The 1DM Sink Control process processes the information from received 1DM traffic units after receiving the MI\_1DM\_Start(iPHB, oPHB, Period) signal. + +The 1DM Source control process generates 1DM messages that pass transparently through MIPs and are received and processed by the 1DM Sink Control process in MEPs. + +On the Source MEP side, the 1DM source control process stamps the value of the Local Time to the TxTimeStampf field in the 1DM message when the first bit of the packet is transmitted. Note that on the sink MEP side, the 1DM sink control process records the value of the Local Time when the last bit of the packet is received. + +#### 8.8.7.2 On-demand DM Source Control process + +The behaviour of the DMMo Control process is defined in Figure 8-48. + +![Flowchart of DMMo Control behaviour. The process starts with 'On-demand DM control' leading to 'Init', then 'MI_DMo_Start (CoS, Period)', and 'Set(0, Timer) count = 0'. It enters a 'Running' state where it branches into 'Timer', 'RI_DMRo(...)', 'MI_DMo_Intermediate_Request', and 'MI_DMo_Terminate'. The 'Timer' path leads to 'DMMo(CoS)' and 'Set(Period, Timer)'. The 'RI_DMRo' path leads to a calculation of 'B_FD[count]' and a decision 'TxTimeStampb = RxTimeStampf = 0?'. If 'N' (No), it sets 'F_FD[count] = Invalid' and 'N_FD[count] = Invalid'. If 'Y' (Yes), it calculates 'F_FD[count] = RxTimeStampf - TxTimeStampf' and 'N_FD[count] = RxTimeb - TxTimeStampb'. Both paths lead to 'count++' and back to the 'Running' state. The 'MI_DMo_Intermediate_Request' and 'MI_DMo_Terminate' paths both lead to 'MI_DMo_Result(count, B_FD[], F_FD[], N_FD[])' and back to the 'Running' state.](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +``` + +graph TD + Start([On-demand DM control]) --> Init([Init]) + Init --> MI_DMo_Start[/MI_DMo_Start (CoS, Period)/] + MI_DMo_Start --> Set_0_Timer[Set(0, Timer) +count = 0] + Set_0_Timer --> Running([Running]) + Running --> Timer[/Timer/] + Running --> RI_DMRo[/RI_DMRo( +TxTimeStampf, +RxTimeStampf, +TxTimeStampb, +RxTimeb, +) /] + Running --> MI_DMo_Intermediate_Request[/MI_DMo_Intermediate_Request/] + Running --> MI_DMo_Terminate[/MI_DMo_Terminate/] + Timer --> DMMo_CoS[/DMMo(CoS)/] + DMMo_CoS --> Set_Period_Timer[Set(Period, Timer)] + Set_Period_Timer --> count_inc[count++] + RI_DMRo --> B_FD_calc[B_FD [count] = (RxTimeb - TxTimeStampf) +- (TxTimeStampb - RxTimeStampf)] + B_FD_calc --> Decision{TxTimeStampb = +RxTimeStampf = 0?} + Decision -- N --> Invalid[ +F_FD[count] = Invalid +N_FD[count] = Invalid +] + Decision -- Y --> FD_calc[ +F_FD[count] = RxTimeStampf - TxTimeStampf +N_FD[count] = RxTimeb - TxTimeStampb +] + Invalid --> count_inc + FD_calc --> count_inc + MI_DMo_Intermediate_Request --> MI_DMo_Result1[/MI_DMo_Result ( +count, B_FD[], F_FD[], N_FD[]) /] + MI_DMo_Terminate --> MI_DMo_Result2[/MI_DMo_Result ( +count, B_FD[], F_FD[], N_FD[]) /] + MI_DMo_Result1 --> Running + MI_DMo_Result2 --> Running + count_inc --> Running + +``` + +Flowchart of DMMo Control behaviour. The process starts with 'On-demand DM control' leading to 'Init', then 'MI\_DMo\_Start (CoS, Period)', and 'Set(0, Timer) count = 0'. It enters a 'Running' state where it branches into 'Timer', 'RI\_DMRo(...)', 'MI\_DMo\_Intermediate\_Request', and 'MI\_DMo\_Terminate'. The 'Timer' path leads to 'DMMo(CoS)' and 'Set(Period, Timer)'. The 'RI\_DMRo' path leads to a calculation of 'B\_FD[count]' and a decision 'TxTimeStampb = RxTimeStampf = 0?'. If 'N' (No), it sets 'F\_FD[count] = Invalid' and 'N\_FD[count] = Invalid'. If 'Y' (Yes), it calculates 'F\_FD[count] = RxTimeStampf - TxTimeStampf' and 'N\_FD[count] = RxTimeb - TxTimeStampb'. Both paths lead to 'count++' and back to the 'Running' state. The 'MI\_DMo\_Intermediate\_Request' and 'MI\_DMo\_Terminate' paths both lead to 'MI\_DMo\_Result(count, B\_FD[], F\_FD[], N\_FD[])' and back to the 'Running' state. + +G.8121.1-Y.1381.1(18)\_F8-48 + +**Figure 8-48 – DMMo Control behaviour** + +Upon receipt of the MI\_DMo\_Start(CoS, Period), the DM protocol is started. Every Period, the generation of a DMM packet is triggered (using the DMMo(CoS) signal) until the MI\_DMo\_Terminate signal is received. Upon receipt of a DMR traffic unit, the Delay value recorded by this particular DMRo traffic unit is calculated. This result is reported using the MI\_DMo\_Result(count, B\_FD[], F\_FD[], N\_FD[]) signal after the receipt of the MI\_DMo\_Terminate signal. Note that the measurements of F\_FD and N\_FD are not supported by peer MEP if both TxTimeStampb and TxTimeStampf are zero. + +#### 8.8.7.3 On-demand DMM Generation process + +The behaviour of the DMM Generation process that is in the DMMo Source control process is defined in Figure 8-49. + + + +``` + +graph TD + A([DMMo Generation]) --> B([Waiting]) + B --> C[/DMMo(CoS, Test ID TLV)/] + C --> D[OAM=DMMo(CoS, Test ID TLV)] + D --> E[TxTimeStampf(OAM)= Local Time] + E --> F[/D(OAM, CoS(CoS), DP(0))/] + F --> B + style A fill:none,stroke:none + style B fill:none,stroke:none + style C fill:none,stroke:none + style D fill:none,stroke:none + style E fill:none,stroke:none + style F fill:none,stroke:none + +``` + +G.8121.1-Y.1381.1(18)\_F8-49 + +Flowchart of DMMo Generation behaviour. The process starts with 'DMMo Generation' (oval), followed by 'Waiting' (oval). It then enters a loop: 'DMMo(CoS, Test ID TLV)' (parallelogram) -> 'OAM=DMMo(CoS, Test ID TLV)' (rectangle) -> 'TxTimeStampf(OAM)= Local Time' (rectangle) -> 'D(OAM, CoS(CoS), DP(0))' (parallelogram). A feedback arrow loops from the output back to the 'Waiting' state. The diagram is labeled G.8121.1-Y.1381.1(18)\_F8-49. + +**Figure 8-49 – DMMo Generation behaviour** + +Upon receiving the DMMo(CoS), a single DMM traffic unit is generated together with the complementing CoS and DP signals. The DA of the generated traffic unit is determined by the DMM(DA) signal. The TxTimeStampf field is assigned the value of the local time. + +The CoS signal value is defined by DMMo(CoS). + +#### 8.8.7.4 On-demand DMM Reception process + +The DMMo Sink Control process processes the received DMMo traffic units and the complementing CoS and DP signals. The behaviour is defined in Figure 8-50. + + + +``` + +graph TD + A([DMMo Reception]) --> B([Waiting]) + B --> C[/D(OAM, CoS(CoS), DP(DP))/] + C --> D[RxTimeStampf(OAM)= Local_Time] + D --> E[/RI_DMMo(OAM, CoS, DP)/] + E --> B + style A fill:none,stroke:none + style B fill:none,stroke:none + style C fill:none,stroke:none + style D fill:none,stroke:none + style E fill:none,stroke:none + +``` + +G.8121.1-Y.1381.1(18)\_F8-50 + +Flowchart of DMMo Reception behaviour. The process starts with 'DMMo Reception' (oval), followed by 'Waiting' (oval). It then enters a loop: 'D(OAM, CoS(CoS), DP(DP))' (parallelogram) -> 'RxTimeStampf(OAM)= Local\_Time' (rectangle) -> 'RI\_DMMo(OAM, CoS, DP)' (parallelogram). A feedback arrow loops from the output back to the 'Waiting' state. The diagram is labeled G.8121.1-Y.1381.1(18)\_F8-50. + +**Figure 8-50 – DMMo Reception behaviour** + +The traffic unit and the complementing CoS and DP signals are forwarded as RI to the DMR Generation process. + +#### 8.8.7.5 On-demand DMR Generation process + +The On-demand DMR Generation process that is in the DMRo Source control process generates a DMRo traffic unit and its complementing CoS and DP signals. The behaviour is defined in Figure 8-51. + + + +``` +graph TD; A([DMRo Generation]) --> B([Waiting]); B --> C[/RI_DMMo(OAM, CoS, DP)/]; C --> D["OPC(OAM)=DMRo
TxTimeStampb(OAM) = Local Time"]; D --> E[/D(OAM), D.CoS(CoS), D.DP(DP)/]; E --> B; +``` + +G.8121.1-Y.1381.1(18)\_F8-51 + +Flowchart of the On-demand DMR Generation process. The steps are: DMRo Generation (oval), Waiting (oval), RI\_DMMo(OAM, CoS, DP) (parallelogram), OPC(OAM)=DMRo, TxTimeStampb(OAM) = Local Time (rectangle), and D(OAM), D.CoS(CoS), D.DP(DP) (parallelogram). A feedback loop connects the final output back to the Waiting step. + +**Figure 8-51 – On-demand DMR Generation behaviour** + +Upon the receipt of RI containing a DMMo traffic unit, the DMR generation process generates a DMR traffic unit and forwards it to the OAM Insertion process. + +As part of the DMR generation: + +- the Opcode is changed into DMRo Opcode; +- the TxTimeStampb field is assigned the value of the Local Time; +- all the other fields (including TLVs and padding after the End TLV) are copied from the RI containing the original DMM traffic unit. + +The TLVs are copied from the RI containing the original DMM traffic unit. If multiple TLVs exist, the order of the TLVs is unchanged. + +#### 8.8.7.6 On-demand DMR Reception process + +The On-demand DMR Reception process that is in the DMRo Sink control process processes the received DMRo traffic units and the complementing CoS and DP signals. The behaviour is defined in Figure 8-52. + + + +``` + +graph TD + A([DMRo Reception]) --> B([Waiting]) + B --> C[/D(OAM), CoS(CoS), DP(DP)/] + C --> D[/RI_DMRo( TxTimeStampf(OAM), RxTimeStampf(OAM), TxTimeStampb(OAM), Local Time)/] + D --> B + +``` + +G.8121.1-Y.1381.1(18)\_F8-52 + +Flowchart of DMRo Reception behaviour. The process starts with 'DMRo Reception' (oval), followed by 'Waiting' (oval). It then enters a loop: 'D(OAM), CoS(CoS), DP(DP)' (parallelogram) leads to 'RI\_DMRo( TxTimeStampf(OAM), RxTimeStampf(OAM), TxTimeStampb(OAM), Local Time)' (parallelogram), which loops back to 'Waiting'. + +**Figure 8-52 – DMR Reception behaviour** + +If the DMR traffic unit is processed, the TxTimeStampf, RxTimeStampf, TxTimeStampb and Test ID are extracted from the traffic unit and signalled together with the Local Time. + +#### 8.8.7.7 On-Demand 1DM Source Control process + +Figure 8-53 shows the behaviour of the on-demand 1DM Source Control process. Upon receipt of the MI\_1DMo\_Start (D, CoS, Period) signal the 1DM protocol is started. The protocol runs until the receipt of the MI\_1DM\_Terminate signal. + +If the On-demand DM protocol is running every Period (as specified in the MI\_1DMo\_Start signal), the generation of a 1DMo message is triggered by generating the 1DMo(CoS) signal towards the 1DMo Generation process. + + + +``` + +graph TD + Start([On-demand 1DMo control So]) --> Init([Init]) + Init --> MI_Start[/MI_1DMo_Start( CoS, Period)/] + MI_Start --> Set0[Set(0, Timer)] + Set0 --> Running([Running]) + Running --> Timer[/Timer/] + Running --> MI_Terminate[/MI_1DMo_Terminate/] + Timer --> IDMCoS[/1DMo(CoS,)/] + IDMCoS --> SetPeriod[Set(Period, Timer)] + SetPeriod --> Running + MI_Terminate --> Init + +``` + +G.8121.1-Y.1381.1(18)\_F8-53 + +Flowchart of On-demand 1DM Source Control behaviour. The process starts with 'On-demand 1DMo control So' (oval), leading to 'Init' (oval), then 'MI\_1DMo\_Start( CoS, Period)' (parallelogram), and 'Set(0, Timer)' (rectangle). It then enters a 'Running' state (oval). From 'Running', it branches to 'Timer' (parallelogram) and 'MI\_1DMo\_Terminate' (parallelogram). 'Timer' leads to '1DMo(CoS,)' (parallelogram) and then 'Set(Period, Timer)' (rectangle). 'MI\_1DMo\_Terminate' loops back to the entry point of 'Init'. 'Set(Period, Timer)' loops back to the entry point of 'Running'. + +**Figure 8-53 – On-demand 1DM Source Control behaviour** + +#### **8.8.7.8 On-Demand 1DM Generation process** + +Figure 8-54 shows the On-demand 1DM Generation process in the 1DM Source control process. Upon receiving the 1DM(CoS) signal, a single 1DM traffic unit is generated by the OAM=1DM (CoS, LocalTime,) call. + +Together with this 1DMo traffic unit, the complementing P and DE signals are generated. The TxTimeStampf field is assigned the value of the Local Time. The value of the P signal is determined by the 1DM(CoS) signal. The DP signal is set to 0. + + + +``` + +graph TD + A([1DMo Generation]) --> B([Waiting]) + B --> C[/1DMo(CoS)/] + C --> D[OAM=1DMo(CoS, LocalTime,)] + D --> E[/D(OAM, CoS(CoS), DP(0))/] + E --> B + +``` + +G.8121.1-Y.1381.1(18)\_F8-54 + +Flowchart of 1DMo Generation behaviour. The process starts with '1DMo Generation' (oval), followed by 'Waiting' (oval), then '1DMo(CoS)' (parallelogram), then 'OAM=1DMo(CoS, LocalTime,)' (rectangle), and finally 'D(OAM, CoS(CoS), DP(0))' (parallelogram). A feedback loop connects the final step back to the 'Waiting' step. The diagram is labeled G.8121.1-Y.1381.1(18)\_F8-54. + +**Figure 8-54 – 1DM Generation behaviour** + +#### 8.8.7.9 On-Demand 1DM Reception process + +The On-demand 1DM Reception process in the 1DM Sink control process processes the received 1DMo traffic units and the complementing P and CoS signals. The behaviour is defined in Figure 8-55. + + + +``` + +graph TD + A([1DMo Reception]) --> B([Waiting]) + B --> C[/D(OAM, CoS(CoS), DP(DP))/] + C --> D[/IDM(TxTimeStampf(OAM), Local Time)/] + D --> B + +``` + +G.8121.1-Y.1381.1(18)\_F8-55 + +Flowchart of 1DM Reception behaviour. The process starts with '1DMo Reception' (oval), followed by 'Waiting' (oval), then 'D(OAM, CoS(CoS), DP(DP))' (parallelogram), and finally 'IDM(TxTimeStampf(OAM), Local Time)' (parallelogram). A feedback loop connects the final step back to the 'Waiting' step. The diagram is labeled G.8121.1-Y.1381.1(18)\_F8-55. + +**Figure 8-55 – 1DM Reception behaviour** + +If the 1DMo traffic unit is processed, the TxTimeStampf fields are extracted and forwarded to the 1DMo Control\_Sk process together with the Local Time using the 1DMo (TxTimeStampf, RxTimef) signal. + +#### 8.8.7.10 On-Demand 1DM Sink Control\_Sk process + +Figure 8-56 shows the behaviour of the on-demand 1DM Sink Control\_Sk process. The protocol runs until the receipt of the MI\_1DM\_Terminate signal. + +While running, the process processes the received $1DMo(TxTimeStamp, RxTimef)$ information. Otherwise the Delay from the single received 1DM traffic unit is calculated. This result is reported using the $MI\_1DMo\_Result(count, N\_FD[])$ signal after the receipt of the $MI\_1DM\_Terminate$ signal. + +![Flowchart of the On-demand 1DM Control_Sk process. The process starts with 'On-demand 1DMo control Sk' leading to 'Init', then 'Count=0', and 'MI_1DMo_Start()'. It then enters a 'Running' state. From 'Running', it branches into three paths: 1) '1DMo(TxTimeStamp, RxTimef)' leading to 'N_FD[count] = RxTimef - TxTimeStamp' and 'count++', which loops back to 'Running'; 2) 'MI_1DMo_Intermediate_Request' leading to 'MI_1DMo_Result(count, N_FD[])'; 3) 'MI_1DMo_Terminate' leading to 'MI_1DMo_Result(count, N_FD[])'. A large feedback loop from the bottom of the 'Running' state returns to the top of the 'Init' state.](7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg) + +``` + +graph TD + Start([On-demand 1DMo control Sk]) --> Init([Init]) + Init --> Count0[Count=0] + Count0 --> MI_1DMo_Start[/MI_1DMo_Start()/] + MI_1DMo_Start --> Running([Running]) + Running --> IDMo[/IDMo(TxTimeStamp, RxTimef)/] + Running --> MI_1DMo_Intermediate_Request[/MI_1DMo_Intermediate_Request/] + Running --> MI_1DMo_Terminate[/MI_1DMo_Terminate/] + IDMo --> N_FD["N_FD[count] = RxTimef - TxTimeStamp
count++"] + N_FD --> Running + MI_1DMo_Intermediate_Request --> MI_1DMo_Result1[/MI_1DMo_Result(count, N_FD[])/] + MI_1DMo_Terminate --> MI_1DMo_Result2[/MI_1DMo_Result(count, N_FD[])/] + MI_1DMo_Result1 --> Running + MI_1DMo_Result2 --> Running + +``` + +G.8121.1-Y.1381.1(18)\_F8-56 + +Flowchart of the On-demand 1DM Control\_Sk process. The process starts with 'On-demand 1DMo control Sk' leading to 'Init', then 'Count=0', and 'MI\_1DMo\_Start()'. It then enters a 'Running' state. From 'Running', it branches into three paths: 1) '1DMo(TxTimeStamp, RxTimef)' leading to 'N\_FD[count] = RxTimef - TxTimeStamp' and 'count++', which loops back to 'Running'; 2) 'MI\_1DMo\_Intermediate\_Request' leading to 'MI\_1DMo\_Result(count, N\_FD[])'; 3) 'MI\_1DMo\_Terminate' leading to 'MI\_1DMo\_Result(count, N\_FD[])'. A large feedback loop from the bottom of the 'Running' state returns to the top of the 'Init' state. + +Figure 8-56 – On-demand 1DM Control\_Sk process + +### 8.8.8 Test (TST) process + +#### 8.8.8.1 Overview + +To support OAM for a dual-ended Throughput (TH) Test, TST as described in clause 8.2.5 of [ITU-T G.8113.1] can be used. The control process specific to the TH Test is for further study. + +Figure 8-57 provides the different processes inside MEPs and MIPs that are involved in the Test Protocol. + + + +``` + +graph LR + subgraph Source + GAI[G-ACh insertion] + OPG[OAM PDU generation] + ISC[1TH source control] + GAI <--> OPG + OPG <--> ISC + end + subgraph MIP [On-demand MIP] + end + subgraph Sink + GAE[G-ACh extraction] + OPR[OAM PDU reception] + ISK[1TH sink control] + GAE <--> OPR + OPR <--> ISK + end + GAI --> MIP + MIP --> GAE + ISC --> MI_1TH_Result_Sent[MI_1TH_Result(Sent)] + ISK --> MI_1TH_Result_Rec[MI_1TH_Result(REC, CRC, BER, OO)] + MI_1TH_Start_S[MI_1TH_Start(CoS, Pattern, Length, Period)] --> ISC + MI_1TH_Terminate_S[MI_1TH_Terminate] --> ISC + MI_1TH_OAM_Tool --> ISC + MI_1TH_Start_P[MI_1TH_Start(Period)] --> ISK + MI_1TH_Terminate_P[MI_1TH_Terminate] --> ISK + MT_CI_S[MT_CI] --> GAI + MI_GAL_Enable_S[MI_GAL_Enable] --> GAI + MT_CI_P[MT_CI] --> GAE + MI_GAL_Enable_P[MI_GAL_Enable] --> GAE + MI_TTLVALUE --> OPG + +``` + +G.8121.1-Y.1381.1(18)\_F8-57 + +Diagram showing the overview of processes involved with the Test Protocol. It consists of three main components: a Source (left), an On-demand MIP (middle), and a Sink (right). The Source contains 'G-ACh insertion', 'OAM PDU generation', and '1TH source control'. The Sink contains 'G-ACh extraction', 'OAM PDU reception', and '1TH sink control'. Various signals like MT\_CI, MI\_GAL\_Enable, MI\_TTLVALUE, MI\_1TH\_Start, MI\_1TH\_Terminate, MI\_1TH\_OAM\_Tool, MI\_1TH\_Result(Sent), and MI\_1TH\_Result(REC, CRC, BER, OO) are shown interacting with these components. + +Figure 8-57 – Overview of processes involved with Test Protocol + +The TST(1TH) protocol is controlled by the TST(1TH) Source Control and TST(1TH) Sink Control processes. The TST(1TH) Source Control process triggers the generation of TST(1TH) traffic units after the receipt of an MI\_1TH\_Start (CoS, Pattern, Length, Period) signal. The TST(1TH) Sink Control process processes the information from received TST traffic units after receiving the MI\_1TH\_Start (Pattern) signal. + +The TST Source control process generates TST messages that pass transparently through MIPs and are received and processed by the TST Sink Control Reception process in MEPs. + +The processes are described in clauses 8.8.8.2 to 8.8.8.5. + +#### **8.8.8.2 TST Source Control process** + +Figure 8-58 defines the behaviour of the TST Source Control process. This process triggers the transmission of TST traffic units after receiving the MI\_Test(CoS, DP, Pattern, Length, Period) signal. The transmission of TST(1TH) traffic units is triggered by the generation of the 1TH(CoS, DP, TLV, TID) signal. This is continued until the receipt of the MI\_1TH\_Terminate signal. After receiving this signal, the number of triggered TST traffic units is reported back using the MI\_1TH\_Result(Sent) signal. + +The TLV field of the 1TH packets is determined by the Generate(Pattern, Length) function. For Pattern, the following types are defined: + +- 0: "Null signal without CRC-32" +- 1: "Null signal with CRC-32" +- 2: "PRBS 231-1 without CRC-32" +- 3: "PRBS 231-1 with CRC-32" + +The Length parameter determines the length of the generated TLV. + +Generate(Pattern, Length) generates a Test TLV with length 'Length' to be included in the 1TH packet. Therefore, this TLV is passed using the 1TH(CoS, DP, TLV, TID) signal to the TST Generation process. + + + +``` + +graph TD + A([ITH Control_So]) --> B([Init]) + B --> C[/MI_ITH(CoS, DP, Pattern, Length, Period)/] + C --> D["Set(0, TxTimer) +Sent=0"] + D --> E([Waiting Test]) + E --> F[/TxTimer/] + E --> G[/MI_ITH_Terminate/] + F --> H["TLV=Generate (Pattern, Length)"] + H --> I[/ITH(CoS, DP, TLV, TID)/] + I --> J["Sent++ +TID++ +Set(Period, TxTimer)"] + G --> K[/MI_ITH_Result (Sent)/] + J --> E + K --> E + +``` + +G.8121.1-Y.1381.1(18)\_F8-58 + +Flowchart of TST Source Control behaviour. The process starts with 'ITH Control\_So' (oval), followed by 'Init' (oval), then 'MI\_ITH(CoS, DP, Pattern, Length, Period)' (parallelogram), and 'Set(0, TxTimer)' and 'Sent=0' (rectangle). It then enters a 'Waiting Test' (oval). From 'Waiting Test', it branches into 'TxTimer' (parallelogram) and 'MI\_ITH\_Terminate' (parallelogram). 'TxTimer' leads to 'TLV=Generate (Pattern, Length)' (rectangle), then 'ITH(CoS, DP, TLV, TID)' (parallelogram), and finally 'Sent++, TID++, Set(Period, TxTimer)' (rectangle). 'MI\_ITH\_Terminate' leads to 'MI\_ITH\_Result (Sent)' (parallelogram). Both 'Sent++, TID++, Set(Period, TxTimer)' and 'MI\_ITH\_Result (Sent)' lead back to the entry point of 'Waiting Test'. A small text 'G.8121.1-Y.1381.1(18)\_F8-58' is at the bottom right. + +**Figure 8-58 – TST Source Control behaviour** + +#### 8.8.8.3 TST Generation process + +Figure 8-59 defines the behaviour of the TST Generation process in Source control process. + + + +``` + +graph TD + A([ITH Generation]) --> B([Waiting]) + B --> C[/ITH(CoS, DP, TLV, TID)/] + C --> D["OAM=TST(TLV, TID)"] + D --> E[/D(OAM, CoS(CoS), DP(DP))/] + E --> B + +``` + +G.8121.1-Y.1381.1(18)\_F8-59 + +Flowchart of TST Generation behaviour. The process starts with 'ITH Generation' (oval), followed by 'Waiting' (oval), then 'ITH(CoS, DP, TLV, TID)' (parallelogram), 'OAM=TST(TLV, TID)' (rectangle), and 'D(OAM, CoS(CoS), DP(DP))' (parallelogram). A feedback loop goes from 'D(OAM, CoS(CoS), DP(DP))' back to the entry point of 'Waiting'. A small text 'G.8121.1-Y.1381.1(18)\_F8-59' is at the bottom right. + +**Figure 8-59 – TST Generation behaviour** + +Upon receiving the 1TH(CoS,DP,TLV,TID), a single 1TH traffic unit is generated together with the complementing CoS and DP signals. The 1TH traffic unit is generated by: + +OAM=1TH(TLV,TID). + +The Transaction Identifier field gets the value of 1TH(TID); the TLV field is populated with TST(TLV). + +The CoS signal is determined by the 1TH(CoS) signal. + +The DP signal is determined by the 1TH(DP) signal. + +#### 8.8.8.4 TST Reception process + +Figure 8-60 defines the behaviour of the TST Reception process that is in the Sink control process. + + + +``` +graph TD; A([1TH Reception]) --> B([Waiting]); B --> C[/D(OAM), CoS(CoS), DP(DP)/]; C --> D[/1TH(TID(OAM), TLV(OAM))/]; D --> B; +``` + +G.8121.1-Y.1381.1(18)\_F8-60 + +Flowchart of the TST Reception process. The process starts with '1TH Reception', followed by 'Waiting', then a decision block 'D(OAM), CoS(CoS), DP(DP)', and finally '1TH(TID(OAM), TLV(OAM))'. A feedback loop connects the final step back to the 'Waiting' state. + +Figure 8-60 – TST Reception behaviour + +#### 8.8.8.5 TST Sink Control process + +Figure 8-61 shows the behaviour of the TST Sink Control process. The MI\_1TH\_Start signal starts the processing of 1TH messages coming from a MEP. The protocol is running until the receipt of the MI\_1TH\_Terminate signal. + +While running, the process processes the received 1TH(rTLV,TID) information. + +First, the received 1TH counter is incremented by one (REC++). Furthermore, if the TLV contains a CRC (Pattern 1 or 3), the CRC counter is incremented by one (CRC++) if the CRC check fails. The function Check(Pattern, TLV) compares the received Test Pattern with the expected Test Pattern. If there is a mismatch, the BERR counter is incremented by one. If the TID value from the RI\_LBR signal does not follow the last received TID value the counter for out of order packets is incremented by one (OO++). + + + +``` + +graph TD + TST[TST Control_Sk] --> Init([Init]) + Init --> MI_1TH_Start[/MI_1TH_Start(Pattern)/] + MI_1TH_Start --> InitVars["OLD_TID=Undef +REC=0 +CRC=0 +BER=0 +OO=0"] + InitVars --> WaitingTest([Waiting Test]) + WaitingTest --> 1TH[/1TH(rTLV, TID)/] + WaitingTest --> MI_1TH_Terminate[/MI_1TH_Terminate/] + WaitingTest --> Timer[/Timer/] + 1TH --> RECinc[REC++] + RECinc --> Decision1{"(Pattern==1 or Pattern==3) && +(CheckCRC(TLV)==Fail)"} + Decision1 -- Y --> CRCinc[CRC++] + Decision1 -- N --> Decision2{"Check(Pattern, TLV)==Fail"} + CRCinc --> Decision2 + Decision2 -- Y --> BERinc[BER++] + Decision2 -- N --> Decision3{"(OLD_TID!=Undef) && +(TID!=OLD_TID+1)"} + BERinc --> Decision3 + Decision3 -- Y --> OOinc[OO++] + Decision3 -- N --> OLD_TID_TID[OLD_TID=TID] + OOinc --> OLD_TID_TID + OLD_TID_TID --> WaitingTest + MI_1TH_Terminate --> SetTimer[Set(5s, Timer)] + SetTimer --> WaitingTest + Timer --> MI_1TH_Result[/MI_1TH_Result( +REC, CRC, BER, OO)/] + MI_1TH_Result --> TST + +``` + +Flowchart of TST Sink Control behaviour. The process starts with 'TST Control\_Sk' leading to 'Init', then 'MI\_1TH\_Start(Pattern)'. It initializes variables: OLD\_TID=Undef, REC=0, CRC=0, BER=0, OO=0. It enters a 'Waiting Test' loop. From 'Waiting Test', three paths emerge: '1TH(rTLV, TID)' which increments REC and checks for pattern and CRC failures; 'MI\_1TH\_Terminate' which sets a 5-second timer; and 'Timer' which leads to 'MI\_1TH\_Result( REC, CRC, BER, OO)'. The '1TH' path includes decision diamonds for '(Pattern==1 or Pattern==3) && (CheckCRC(TLV)==Fail)', 'Check(Pattern, TLV)==Fail', and '(OLD\_TID!=Undef) && (TID!=OLD\_TID+1)'. Failures in these checks increment CRC, BER, and OO counters respectively. After 'OLD\_TID=TID', the flow returns to 'Waiting Test'. A final return path goes from 'MI\_1TH\_Result' back to 'TST Control\_Sk'. + +G.8121.1-Y.1381.1(18)\_F8-61 + +**Figure 8-61 – TST Sink Control behaviour** + +### 8.8.9 Route Tracing (RT) + +For further study. + +### 8.8.10 LCK/AIS Reception + +See clause 8.8.10 of [ITU-T G.8121]. + +# 9 MPLS-TP processes + +## 9.1 Connection functions (MT\_C) + +See clause 9.1 of [ITU-T G.8121]. + +### 9.1.1 Sub-network connection protection process + +See clause 9.1.1 of [ITU-T G.8121]. + +## 9.2 Termination functions + +### 9.2.1 MPLS-TP Trail Termination function (MT\_TT) + +The bidirectional MPLS-TP Trail Termination (MT\_TT) function terminates the MPLS-TP OAM to determine the status of the MPLS-TP (sub)layer trail. The MT\_TT function is performed by a co-located pair of the MPLS-TP trail termination source (MT\_TT\_So) and sink (MT\_TT\_Sk) functions, as shown in Figure 9-1. + + + +The diagram shows two triangular blocks labeled 'MT'. The left 'MT' block has an input arrow labeled 'MT\_AP' pointing down into it and an output arrow labeled 'MT\_TCP' pointing down from it. The right 'MT' block has an output arrow labeled 'MT\_AP' pointing up from it and an input arrow labeled 'MT\_TCP' pointing up into it. A horizontal double-headed arrow labeled 'MT\_RP' connects the two 'MT' blocks. Below the diagram is the text 'G.8121.1-Y.1381.1(13)\_F9-1'. + +Diagram of the MT\_TT function showing two MT blocks connected by an MT\_RP signal. Each MT block has an MT\_AP input and an MT\_TCP output. + +Figure 9-1 – MT\_TT + +#### 9.2.1.1 MPLS-TP Trail Termination Source function (MT\_TT\_So) + +The MT\_TT\_So function determines and inserts the time-to-live (TTL) value in the shim header TTL field and adds MPLS-TP OAM for pro-active monitoring to the MT\_AI signal at its MT\_AP. + +##### Symbol + +The MT\_TT\_So function symbol is shown in Figure 9-2. + + + +The diagram shows a triangular block labeled 'MT'. It has an input arrow labeled 'MT\_AP' pointing down into it from the top. It has two input arrows labeled 'MT\_TT\_So\_MP' and 'MT\_TT\_So\_TP' pointing into it from the left. It has an output arrow labeled 'MT\_RP' pointing to the right. It has an output arrow labeled 'MT\_TCP' pointing down from it. Below the diagram is the text 'G.8121.1-Y.1381.1(13)\_F9-2'. + +Diagram of the MT\_TT\_So function symbol showing an MT block with multiple inputs and outputs. + +Figure 9-2 – MT\_TT\_So function + +##### Interfaces + +Table 9-1 – MT\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------| +| MT_AP:
MT_AI_D
MT_AI_PHB
MT_RP:
MT_RI_CC_RDI
MT_RI_CC_Blk
MT_RI_CC_RxFCl
MT_RI_CC_TxFCl
MT_RI_OAM_Info(D,CoS,DP)
MT_TT_So_MP:
MT_TT_So_MI_GAL_Enable
MT_TT_So_MI_TTLVALUE
MT_TT_So_MI_MEG_ID
MT_TT_So_MI_MEP_ID
MT_TT_So_MI_CC_OAM_Tool
MT_TT_So_MI_RDI_OAM_Tool
MT_TT_So_MI_LMC_Enable
MT_TT_So_MI_CC_CoS
MT_TT_So_MI_CC_Period
MT_TT_So_MI_CC_Enable (Note)
MT_TT_So_MI_LMp_OAM_Tool
MT_TT_So_MI_LML_Enable[1...M_LMp]
MT_TT_So_MI_LMp_Period[1...M_LMp]
MT_TT_So_MI_LMp_CoS[1...M_LMp]
MT_TT_So_MI_DMp_OAM_Tool
MT_TT_So_MI_DMp_Enable[1...M_DMp]
MT_TT_So_MI_DMp_Period[1...M_DMp]
MT_TT_So_MI_DMp_Test_ID[1...M_DMp]
MT_TT_So_MI_DMp_CoS[1...M_DMp]
MT_TT_So_MI_DMp_Length[1...M_DMp] | MT_TCP:
MT_CI_D
MT_CI_oPHB
MT_CI_iPHB
MT_RP: | + +**Table 9-1 – MT\_TT\_So inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| MT_TT_So_MI_1DMp_OAM_Tool
MT_TT_So_MI_1DMp_Enable[1...M 1DMp ]
MT_TT_So_MI_1DMp_Period[1...M 1DMp ]
MT_TT_So_MI_1DMp_Test_ID[1...M 1DMp ]
MT_TT_So_MI_1DMp_Length[1...M 1DMp ]
MT_TT_So_MI_1DMp_CoS[1...M 1DMp ]
MT_TP:
MT_TT_So_TI_TimeStamp1 | | +| NOTE – MI_CVp_Enable defined in [ITU-T G.8121] is automatically configured true by setting MI_CC_Enable true. | | + +##### Processes + +The processes associated with the MT\_TT\_So function are as depicted in Figure 9-3. + +![Figure 9-3 – MT_TT_So process diagram. This block diagram shows the internal components of the MT_TT_So process. At the top, inputs AI_D and AI_PHB enter a 'Block' component. The output of 'Block' goes to 'Insert TTL', which then goes to 'PHB', then to a 'counter'. The output of this 'counter' enters a large 'MEP proactive OAM G-Ach insertion' block. Inside this block, the data path goes through 'PDU', 'TTL', 'PHB', and 'Channel type' components. The 'MEP proactive OAM G-Ach insertion' block has a 'TxFC' output and a 'TxFC[]' output. The 'TxFC' output goes to an 'OAM PDU generation' block, which in turn goes to a 'Proactive OAM source control' block. The 'Proactive OAM source control' block has a 'MI_TimeStamp' output. The output of the 'Proactive OAM source control' block goes to another 'counter' block. The output of this 'counter' goes to 'CI_D', 'CI_oPHB', and 'CI_iPHB' components, which then exit the main process block. To the right of the main process block, there are several management interface (MI) inputs: 'RI_CC_Blk', 'RI_CC_RDI', 'RI_CC_RTxFCI', 'RI_CC_TRxFcf', 'RI_OAM_Info(D, CoS, DP)', 'MI_TTLVALUE', 'MI_GAL_Enable', 'MI_MEG_ID', 'MI_MEP_ID', 'MI_CC_OAM_Tool', 'MI_RDI_OAM_Tool', 'MI_CC_Enable', 'MI_LMC_Enable', 'MI_DMp_OAM_Tool', 'MI_DMp_Enable[1...M_DMp]', 'MI_DMp_Period[1...M_DMp]', 'MI_DMp_CoS[1...M_DMp]', 'MI_1DMp_OAM_Tool', 'MI_1DMp_Enable[1...M_1DMp]', 'MI_1DMp_Period[1...M_1DMp]', 'MI_1DMp_Lenght[1...M_1DMp]', and 'MI_1DMp_CoS[1...M_1DMp]'. These MI inputs are connected to the 'MEP proactive OAM G-Ach insertion', 'OAM PDU generation', and 'Proactive OAM source control' blocks. The diagram is labeled with 'MT_AP' at the top, 'MT_TT_So_MP' and 'MT_TP' on the right, and 'MT_TCP' at the bottom. A reference 'G.8121.1-Y.1381.1(16)_F9-3' is also present.](fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg) + +Figure 9-3 – MT\_TT\_So process diagram. This block diagram shows the internal components of the MT\_TT\_So process. At the top, inputs AI\_D and AI\_PHB enter a 'Block' component. The output of 'Block' goes to 'Insert TTL', which then goes to 'PHB', then to a 'counter'. The output of this 'counter' enters a large 'MEP proactive OAM G-Ach insertion' block. Inside this block, the data path goes through 'PDU', 'TTL', 'PHB', and 'Channel type' components. The 'MEP proactive OAM G-Ach insertion' block has a 'TxFC' output and a 'TxFC[]' output. The 'TxFC' output goes to an 'OAM PDU generation' block, which in turn goes to a 'Proactive OAM source control' block. The 'Proactive OAM source control' block has a 'MI\_TimeStamp' output. The output of the 'Proactive OAM source control' block goes to another 'counter' block. The output of this 'counter' goes to 'CI\_D', 'CI\_oPHB', and 'CI\_iPHB' components, which then exit the main process block. To the right of the main process block, there are several management interface (MI) inputs: 'RI\_CC\_Blk', 'RI\_CC\_RDI', 'RI\_CC\_RTxFCI', 'RI\_CC\_TRxFcf', 'RI\_OAM\_Info(D, CoS, DP)', 'MI\_TTLVALUE', 'MI\_GAL\_Enable', 'MI\_MEG\_ID', 'MI\_MEP\_ID', 'MI\_CC\_OAM\_Tool', 'MI\_RDI\_OAM\_Tool', 'MI\_CC\_Enable', 'MI\_LMC\_Enable', 'MI\_DMp\_OAM\_Tool', 'MI\_DMp\_Enable[1...M\_DMp]', 'MI\_DMp\_Period[1...M\_DMp]', 'MI\_DMp\_CoS[1...M\_DMp]', 'MI\_1DMp\_OAM\_Tool', 'MI\_1DMp\_Enable[1...M\_1DMp]', 'MI\_1DMp\_Period[1...M\_1DMp]', 'MI\_1DMp\_Lenght[1...M\_1DMp]', and 'MI\_1DMp\_CoS[1...M\_1DMp]'. These MI inputs are connected to the 'MEP proactive OAM G-Ach insertion', 'OAM PDU generation', and 'Proactive OAM source control' blocks. The diagram is labeled with 'MT\_AP' at the top, 'MT\_TT\_So\_MP' and 'MT\_TP' on the right, and 'MT\_TCP' at the bottom. A reference 'G.8121.1-Y.1381.1(16)\_F9-3' is also present. + +Figure 9-3 – MT\_TT\_So process diagram + +**PHB:** See clause 9.2 of [ITU-T G.8121]. + +**Extract TTL:** See clause 9.2 of [ITU-T G.8121]. + +**Block:** See clause 9.2 of [ITU-T G.8121]. + +**Counter:** A counter is used to count packets for proactive loss measurements. See clause 8.8.1.4 for the upper counter in Figure 9-3 and clause 8.8.4.7 for the lower counter in Figure 9-3. + +**G-ACH/GAL Insertion:** See clause 8.1 of [ITU-T G.8121]. + +**Pro-active OAM Source Control:** This process consists of the sub-processes shown in Figure 9-4. These details are in clause 8.8. + + + +The diagram illustrates the Pro-active OAM Source Control process. It consists of seven control blocks arranged vertically, each with associated parameters. The blocks are: CC control, RDI control, LMMp control (stacked), DMMp control (stacked), IDMp control (stacked), LMRp control (stacked), and DMRp control (stacked). Arrows point from each block to its corresponding parameter list. + +- CC control**: MI\_MEG\_ID, MI\_MEP\_ID, MI\_CC\_OAM\_Tool, MI\_CC\_Enable, MI\_CC\_CoS, MI\_CC\_Period, TxFC +- RDI control**: MI\_RDI\_OAM\_Tool, RI\_CC\_RD[] +- LMMp control**: MI\_LMp\_OAM\_Tool, MI\_LML\_Enable[1...M\_LMp], MI\_LMp\_Period[1...M\_LMp], MI\_LMp\_CoS[1...M\_LMp], TxFC[] +- DMMp control**: MI\_DMp\_OAM\_Tool, MI\_DMp\_Enable[1...M\_DMp], MI\_DMp\_Period[1...M\_DMp], MI\_DMP\_Test\_ID[1...M\_DMp], MI\_DMp\_CoS[1...M\_DMp], MI\_DMp\_Length[1...M\_DMp], TI\_TimeStamp[] +- IDMp control**: MI\_IDMp\_OAM\_Tool, MI\_IDMp\_Enable[1...M\_IDMp], MI\_IDMp\_Period[1...M\_IDMp], MI\_DMP\_Test\_ID[1...M\_DMp], MI\_IDMp\_Length[1...M\_IDMp], MI\_IDMp\_P[1...M\_IDMp], TI\_TimeStamp[] +- LMRp control**: MI\_LMp\_OAM\_Tool, MI\_LML\_Enable[1...M\_LMp], RI\_OAM\_Info(D, CoS, DP), TxFC[] +- DMRp control**: MI\_DMp\_OAM\_Tool, MI\_DMM\_Enable[1...M\_DMp], RI\_OAM\_Info(D, CoS, DP) + +G.8121.1-Y.1381.1(16)\_F9-4 + +Diagram of Pro-active OAM Source Control process showing control blocks and their associated parameters. + +**Figure 9-4 – Pro-active OAM Source Control process** + +**OAM PDU Generation process:** See clause 9.2 of [ITU-T G.8121]. + +##### **Defects** + +None. + +###### **Consequent actions** + +None. + +##### **Defect correlations** + +None. + +##### **Performance monitoring** + +None. + +#### 9.2.1.2 MPLS-TP Trail Termination Sink function (MT\_TT\_Sk) + +The MT\_TT\_Sk function reports the state of the MPLS-TP Trail (Network Connection). It extracts MPLS-TP trail OAM – for pro-active monitoring – from the MPLS-TP signal at its MT\_TCP, detects defects, counts during 1 s periods errors and defects to feed PM when connected and forwards the defect information as backward indications to the companion MT\_TT\_So function. + +NOTE – The MT\_TT\_Sk function extracts and processes one level of MPLS-TP OAM irrespective of the presence of more levels. + +##### Symbol + +The MT\_TT\_Sk function symbol is shown in Figure 9-5. + + + +G.8121.1-Y.1381.1(13)\_F9-5 + +Diagram of the MT\_TT\_Sk function symbol. It features a central triangle labeled 'MT'. Above the triangle is 'MT\_AP' with an upward-pointing arrow. Below the triangle is 'MT\_TCP' with an upward-pointing arrow. To the left of the triangle is 'MT\_TT\_Sk\_MP' with a double-headed horizontal arrow. To the right of the triangle is 'MT\_RP' with a double-headed horizontal arrow. Below the diagram is the text 'G.8121.1-Y.1381.1(13)\_F9-5'. + +Figure 9-5 – MT\_TT\_Sk function + +##### Interfaces + +Table 9-2 – MT\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MT_TCP:
MT_CI_D
MT_CI_iPHB
MT_CI_oPHB
MT_CI_SSF
MT_CI_Lstack
MT_RP:
MT_TT_Sk_MP:
MT_TT_Sk_MI_GAL_Enable
MT_TT_Sk_MI_MEG_ID
MT_TT_Sk_MI_PeerMEP_ID
MT_TT_Sk_MI_CC_OAM_Tool
MT_TT_Sk_MI_RDI_OAM_Tool
MT_TT_Sk_MI_CC_Enable (Note)
MT_TT_Sk_MI_LMC_Enable
MT_TT_Sk_MI_CC_Period
MT_TT_Sk_MI_CC_CoS
MT_TT_Sk_MI_Get_SvdCC
MT_TT_Sk_MI_LM_DEGM
MT_TT_Sk_MI_LM_M
MT_TT_Sk_MI_LM_DEGTHR
MT_TT_Sk_MI_LM_TFMIN
MT_TT_Sk_MI_LMp_OAM_Tool [1... M LMp ]
MT_TT_Sk_MI_LML_Enable[1... M LMp ]
MT_TT_Sk_MI_LMp_CoS[1... M LMp ]
MT_TT_Sk_MI_DMp_OAM_Tool[1... M DMp ]
MT_TT_Sk_MI_DMp_Enable[1... M DMp ]
MT_TT_Sk_MI_DMp_CoS[1... M DMp ]
MT_TT_Sk_MI_1DMp_OAM_Tool[1...M 1DMp ]
MT_TT_Sk_MI_1DMp_Enable[1...M 1DMp ]
MT_TT_Sk_MI_1DMp_Test_ID[1...M 1DMp ]
MT_TT_Sk_MI_AIS_OAM_Tool
MT_TT_Sk_MI_LCK_OAM_Tool
MT_TT_Sk_MI_1second
MT_TP:
MT_TT_Sk_TI_TimeStamp1 | MT_AP:
MT_AI_D
MT_AI_PHB
MT_AI_TSF
MT_AI_TSD
MT_AI_AIS
MT_AI_LStack
MT_RP:
MT_RI_CC_RDI
MT_RI_CC_Blk
MT_RI_CC_RxFCl
MT_RI_CC_TxFCl
MT_RI_OAM_Info(D,CoS,DP)
MT_TT_Sk_MP:
MT_TT_Sk_MI_SvdCC
MT_TT_Sk_MI_cSSF
MT_TT_Sk_MI_cLCK
MT_TT_Sk_MI_cLOC
MT_TT_Sk_MI_cMMG
MT_TT_Sk_MI_cUNM
MT_TT_Sk_MI_cUNP
MT_TT_Sk_MI_cUNC
MT_TT_Sk_MI_cDEG
MT_TT_Sk_MI_cRDI
MT_TT_Sk_MI_pN_LF[1...P]
MT_TT_Sk_MI_pN_TF[1...P]
MT_TT_Sk_MI_pF_LF[1...P]
MT_TT_Sk_MI_pF_TF[1...P]
MT_TT_Sk_MI_pF_DS
MT_TT_Sk_MI_pN_DS
MT_TT_Sk_MI_pB_FD[1...P]
MT_TT_Sk_MI_pB_FDV[1...P]
MT_TT_Sk_MI_pN_FD[1...P]
MT_TT_Sk_MI_pN_FDV[1...P]
MT_TT_Sk_MI_pF_FD[1...P]
MT_TT_Sk_MI_pF_FDV[1...P] | +| NOTE – MI_CVp_Enable defined in [ITU-T G.8121] is automatically configured true by setting MI_CC_Enable true. | | + +##### Processes + +The processes associated with the MT\_TT\_Sk function are as depicted in Figure 9-6. + + + +Figure 9-6 – MT\_TT\_Sk process diagram. This is a complex block diagram showing the internal processes of the MT\_TT\_Sk function. It is divided into three main horizontal sections: MT\_RP (top), MT\_TT\_Sk\_MP (middle), and MT\_AP (bottom). The diagram shows various functional blocks like 'Consequent actions', 'Defect correlation', 'Defect generation', 'Performance monitoring', 'Performance counter', 'Proactive OAM sink control', 'OAM PDU reception', 'Block', 'Extract TTL', 'PHB', 'Counter', and 'MEP proactive OAM G-Ach extraction'. It also lists numerous Management Information (MI) objects and signals such as RI\_CC\_RDI, RI\_CC\_Blk, RI\_CC\_RxFCl, RI\_CC\_TxFCl, RI\_OAM\_Info, MI\_LM\_DEGM, MI\_LM\_M, MI\_LM\_DEGTHR, MI\_LM\_TFMIN, MI\_cSSF, MI\_cLCK, MI\_cLOC, MI\_cMMG, MI\_cUNM, MI\_cUNP, MI\_cUNC, MI\_cDEG, MI\_cRDI, MI\_pN\_TF, MI\_pN\_LF, MI\_pF\_TF, MI\_pF\_LF, MI\_pF\_DS, MI\_pN\_DS, MI\_pB\_FD, MI\_pB\_FDV, MI\_pN\_FD, MI\_pN\_FDV, MI\_pF\_FD, MI\_pF\_FDV, MI\_lsecond, MI\_SvdCC, MI\_MEG\_ID, MI\_PeerMEP\_ID, MI\_CC\_Period, MI\_Get\_SvdCC, MI\_CC\_CoS, MI\_CC\_Enable, MI\_LMC\_Enable, MI\_CC\_OAM\_Tool, MI\_RDI\_OAM\_Tool, MI\_AIS\_OAM\_Tool, MI\_LCK\_OAM\_Tool, MI\_LMp\_OAM\_Tool, MI\_LML\_Enable, MI\_LMp\_CoS, MI\_DMp\_OAM\_Tool, MI\_DMp\_Enable, MI\_DMp\_CoS, MI\_IDMp\_OAM\_Tool, MI\_IDMp\_Enable, MI\_IDMp\_Test\_ID, MI\_GAL\_Enable, and MI\_TimeStamp. Signals like AI\_TSF, AI\_TSD, AI\_AIS, AI\_PHB, AI\_D, and AI\_L\_Stack are shown at the top, while CI\_SSF, CI\_oPHB, CI\_iPHB, CI\_D, and CI\_L\_Stack are at the bottom. Arrows indicate the flow of data and control between these elements. + +Figure 9-6 – MT\_TT\_Sk process diagram + +**PHB:** The CI\_oPHB signal is assigned to the AI\_PHB signal at the reference point MT\_AP. + +Note that the CI\_iPHB signal is not used by any of the processes in the function. + +**Extract TTL:** The TTL value is extracted from the outer shim header's TTL field within the MT\_CI traffic unit. + +**Block:** When the aBlock consequent action is asserted, this process drops all traffic units arriving at its input. + +**Counter:** A counter is used to count packets for proactive loss measurements. See clause 8.8.1.4 for the upper counter in Figure 9-6 and clause 8.8.4.7 for the lower counter in Figure 9-6. + +**G-ACh/GAL Extraction:** See clause 8.1 of [ITU-T G.8121]. + +**Pro-active OAM Sink Control:** This process consists of the sub-processes shown in Figure 9-7. The details are in clause 8.8. + +![Figure 9-7 – Pro-active OAM Sink Control process diagram. The diagram shows a central 'Proactive OAM sink control' block (dashed box) containing several sub-processes: CC control, RDI control, LMRp control, DMRp control, DMRp control, LMMp control, DMMp control, AIS control, and LCK control. External inputs include MI_MEG_ID, MI_PeerMEP_ID, MI_CC_Period, MI_Get_SvdCC, MI_CC_P, MI_CC_Enable, RxFC, MI_SvdCC, MI_LMp_OAM_Tool, MI_LML_Enable[1...M_LMp], RxFCI, MI_DMp_OAM_Tool, MI_DMp_Enable[1...M_DMp], TI_TimeStamp1, MI_IDMp_OAM_Tool, MI_IDMp_Enable[1...M_IDMp], TI_TimeStamp1, MI_LMp_OAM_Tool, MI_LML_Enable[1...M_LMp], RxFCI, RI_OAM_Info(D, CoS, DP), MI_DMp_OAM_Tool, MI_DMp_Enable[1...M_DMp], RI_OAM_Info(D, CoS, DP), MI_AIS_OAM_Tool, and MI_LCK_OAM_Tool. External outputs include expCC, unexpMEG, unexpMEP, unexpPeriod, unexpCoS, TxFCI, RxFC, TxRCb, RxFCb, dRDI, DMP result, IDMP result, dAIS, and dLCK. The right side is labeled 'OAM PDU reception' and includes labels CC, RDI, LMRp, DMRp, DMRp, LMMp, DMMp, AIS, and LCK. A small note at the bottom right reads 'G.8121.1-Y.1381.1(16)-Cor.1(16)_F9-7'.](f8f8916ae391a1233c13ce738c699109_img.jpg) + +Figure 9-7 – Pro-active OAM Sink Control process diagram. The diagram shows a central 'Proactive OAM sink control' block (dashed box) containing several sub-processes: CC control, RDI control, LMRp control, DMRp control, DMRp control, LMMp control, DMMp control, AIS control, and LCK control. External inputs include MI\_MEG\_ID, MI\_PeerMEP\_ID, MI\_CC\_Period, MI\_Get\_SvdCC, MI\_CC\_P, MI\_CC\_Enable, RxFC, MI\_SvdCC, MI\_LMp\_OAM\_Tool, MI\_LML\_Enable[1...M\_LMp], RxFCI, MI\_DMp\_OAM\_Tool, MI\_DMp\_Enable[1...M\_DMp], TI\_TimeStamp1, MI\_IDMp\_OAM\_Tool, MI\_IDMp\_Enable[1...M\_IDMp], TI\_TimeStamp1, MI\_LMp\_OAM\_Tool, MI\_LML\_Enable[1...M\_LMp], RxFCI, RI\_OAM\_Info(D, CoS, DP), MI\_DMp\_OAM\_Tool, MI\_DMp\_Enable[1...M\_DMp], RI\_OAM\_Info(D, CoS, DP), MI\_AIS\_OAM\_Tool, and MI\_LCK\_OAM\_Tool. External outputs include expCC, unexpMEG, unexpMEP, unexpPeriod, unexpCoS, TxFCI, RxFC, TxRCb, RxFCb, dRDI, DMP result, IDMP result, dAIS, and dLCK. The right side is labeled 'OAM PDU reception' and includes labels CC, RDI, LMRp, DMRp, DMRp, LMMp, DMMp, AIS, and LCK. A small note at the bottom right reads 'G.8121.1-Y.1381.1(16)-Cor.1(16)\_F9-7'. + +**Figure 9-7 – Pro-active OAM Sink Control process** + +**OAM PDU Receptions:** See clause 8.8 of [ITU-T G.8121]. + +**Defect Generation:** This process raises and clears the defects as defined in clause 6.1 of [ITU-T G.8121] that are dLOC, dMMG, dUNM, dDEG, dUNP, dUNPr, dRDI, dAIS, dLCK. + +##### Defects + +This function detects dLOC[i], dUNL, dMMG, dUNM, dDEG, dUNP, dUNPr, dRDI[i], dAIS, dLCK. + +##### Consequent actions + +aBLK $\leftarrow$ (dUNL or dMMG or dUNM) + +Note that dUNP and dUNPr do not contribute to aBLK, because a mismatch of periodicity is not considered to be a security issue. + +aTSF $\leftarrow$ (dLOC and MI\_CC\_Enable) or (dAIS and not(MI\_CC\_Enable)) or (dLCK and not(MI\_CC\_Enable)) or dUNL or dMMG or dUNM or CI\_SSF + +aTSD $\leftarrow$ dDEG and (not aTSF) + +aAIS $\leftarrow$ aTSF + +aRDI $\leftarrow$ aTSF + +##### Defect correlations + +cLOC[i] $\leftarrow$ dLOC[i] and (not dAIS) and (not dLCK) and (not CI\_SSF) and (MI\_CC\_Enable) + +cUNL $\leftarrow$ dUNL + +cMMG $\leftarrow$ dMMG + +cUNM $\leftarrow$ dUNM + +cDEG[1] $\leftarrow$ dDEG[1] and (not dAIS) and (not dLCK) and (not CI\_SSF) and (not (dLOC[1..n] or dUNL or dMMG or dUNM)) and (MI\_CC\_Enable)) + +cUNP $\leftarrow$ dUNP + +cUNPr $\leftarrow$ dUNPr + +cRDI $\leftarrow$ (dRDI[1..n]) and (MI\_CC\_Enable) + +cSSF $\leftarrow$ CI\_SSF or dAIS + +cLCK $\leftarrow$ dLCK and (not dAIS) + +##### Performance monitoring + +pN\_TF $\leftarrow$ N\_TF + +pN\_LF $\leftarrow$ N\_LF + +pF\_TF $\leftarrow$ F\_TF + +pF\_LF $\leftarrow$ F\_LF + +pN\_DS $\leftarrow$ aTSF + +pF\_DS $\leftarrow$ aRDI[1] + +pB\_FD $\leftarrow$ B\_FD + +pB\_FDV $\leftarrow$ B\_FDV + +pF\_FD $\leftarrow$ F\_FD + +pF\_FDV $\leftarrow$ F\_FDV + +pN\_FD $\leftarrow$ N\_FD + +pN\_FDV $\leftarrow$ N\_FDV + +## 9.3 Adaptation functions + +### 9.3.1 MPLS-TP to MPLS-TP adaptation function (MT/MT\_A) + +This atomic functions are defined in clause 9.3.1 of [ITU-T G.8121]. They use the OAM protocol specific AIS insertion process and LCK generation process as defined in clauses 8.6.2 and 8.6.3, respectively. + +## 9.4 MT diagnostic functions + +### 9.4.1 MT diagnostic functions for MEP (MTDe) + +The bidirectional MTDe Frail Termination (MTDe\_TT) function is performed by a co-located pair of MTDe flow termination source (MTDe\_TT\_So) and sink (MTDe\_TT\_Sk) functions as shown in Figure 9-8. + + + +The diagram illustrates the MTDe\_TT function. It consists of two MTDe blocks, each represented by a downward-pointing triangle. The left MTDe block has an input arrow labeled MTDe\_AP pointing to its top vertex and an output arrow labeled MT\_TCP pointing from its bottom vertex. The right MTDe block has an output arrow labeled MTDe\_AP pointing from its top vertex and an input arrow labeled MT\_TCP pointing to its bottom vertex. A horizontal double-headed arrow labeled MTDe\_RP connects the two MTDe blocks. Below the diagram is the text G.8121.1-Y.1381.1(13)\_F9-8. + +Diagram of MTDe\_TT function showing two MTDe blocks connected by MTDe\_RP. Each MTDe block is connected to an MTDe\_AP and an MT\_TCP. + +Figure 9-8 – MTDe\_TT + +#### 9.4.1.1 MT diagnostic source function for MEP (MTDe\_TT\_So) + +##### Symbol + +The MTDe\_TT\_So function symbol is shown in Figure 9-9. + + + +The diagram shows the symbol for the MTDe\_TT\_So function. It features a central MTDe block, represented by a downward-pointing triangle. An input arrow labeled MT\_AP points to its top vertex. An output arrow labeled MT\_TCP points from its bottom vertex. A horizontal double-headed arrow labeled MT\_TT\_So\_MP points to its left vertex. A horizontal double-headed arrow labeled MT\_RP points to its right vertex. Below the diagram is the text G.8121.1-Y.1381.1(13)\_F9-9. + +Symbol for MTDe\_TT\_So function showing an MTDe block with multiple input and output arrows. + +Figure 9-9 – MTDe\_TT\_So symbol + +##### Interfaces + +**Table 9-3 – MTDe\_TT\_So interfaces** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MTDe_AP:
MTDe_AI_D
MTDe_AI_oPHB
MTDe_AI_iPHB
MTDe_TT_RP:
MTDe_RI_LMRo(TxFCf,RxFCf,TxFCb,RxFCb,CoS)
MTDe_RI_DMRo(TxTimeStampf,RxTimeStampf,
TxTimeStampb,RxTimeb,CoS)
MTDe_RI_LMMo(D, CoS, DP)
MTDe_RI_DMMo(D, CoS, DP)
MTDe_RI_CVM(D, CoS, DP)
MTDe_RI_CVR(rTLV, TID)
MTDe_TT_So_MP:
MTDe_TT_So_MI_GAL_Enable
MTDe_TT_So_MI_TTLVALUE
MTDe_TT_So_MI_MEP_ID
MTDe_TT_So_MI_CV_OAM_Tool
MTDe_TT_So_MI_CV_Series (Target MEP/MIP
ID,CoS,N,Length,Period)
MTDe_TT_So_MI_CV_Test(CoS, Pattern, Length,Period)
MTDe_TT_So_MI_CV_Terminate
MTDe_TT_So_MI_1TH_OAM_Tool
MTDe_TT_So_MI_1TH_Start(CoS, Pattern,
Length,Period)
MTDe_TT_So_MI_1TH_Terminate
MTDe_TT_So_MI_LMo_OAM_Tool[1...M LMo ]
MTDe_TT_So_MI_LMo_Start(CoS,Period) [1...M LMo ]
MTDe_TT_So_MI_LMo_Intermediate_Request[1...M LMo ]
MTDe_FT_So_MI_LMo_Terminate[1...M LMo ]
MTDe_TT_So_MI_DMo_OAM_Tool[1...M DMo ]
MTDe_TT_So_MI_DMo_Start (CoS, ,Period)[1...M DMo ]
MTDe_TT_So_MI_DMo_Intermediate_Request[1...M DMo ]
MTDe_TT_So_MI_DMo_Terminate[1...M DMo ]
MTDe_TT_So_MI_1DMo_OAM_Tool[1...M 1DMo ]
MTDe_TT_So_MI_1DMo_Start (CoS, Period)[1...M 1DMo ]
MTDe_TT_So_MI_1DMo_Terminate[1...M 1DMo ]
MTDe_TT_So_TP:
MTDe_TT_So_TI_TimeStampI | MT_TCP:
MT_CI_D
MT_CI_oPHB
MT_CI_iPHB
MTDe_TT_So_MP:
MTDe_TT_So_MI_CV_Series_Result(REC,ERR,OO)
MTDe_TT_So_MI_CV_Test_Result(Sent, REC,
REC,ERR,OO)
MTDe_TT_So_MI_1TH_Result(Sent)
MTDe_TT_So_MI_LMo_Result(N_TF,N_LF,F_TF,F
_LF)[1...M LMo ]
MTDe_TT_So_MI_DMo_Result(count,B_FD[],F_FD[
],N_FD[])[1...M DMo ] | + +##### Processes + +The processes associated with the MTDe\_TT\_So function are as depicted in Figure 9-10. + +![Figure 9-10 – MTDe_TT_So process diagram. The diagram shows the internal components and data flows of the MTDe_TT_So process. At the top, inputs AI_D and AI_iPHB/oPHB enter a 'counter' block. The 'counter' block connects to a 'MEP on-demand G-ACh insertion' block. This block outputs PDU, TTL, Channel type, and PHB to an 'OAM PDU generation process' block. The 'OAM PDU generation process' block connects to an 'On-demand OAM source control' block. The 'On-demand OAM source control' block outputs TxFCI[] to the 'MEP on-demand G-ACh insertion' block. At the bottom, the 'MEP on-demand G-ACh insertion' block outputs CI_D, CI_oPHB, CI_iPHB, and MT_TCP. To the right of the diagram, a list of management interfaces is provided, categorized by MTDe_RP, MTDe_TT_So_MP, and MTDe_TT_So_TP. The interfaces include RI_CVM, RI_LMMo, RI_DMMo, RI_LMRo, RI_DMRo, MI_CV_Series_Result, MI_ITH_Result, MI_LMo_Result, MI_CV_Test_Result, MI_DMo_Result, MI_GAL_Enable, MI_TTLVALUE, MI_MEP_ID, MI_CV_OAM_Tool, MI_CV_Series, MI_CV_Test, MI_CV_Terminate, MI_ITH_OAM_Tool, MI_ITH_Start, MI_ITH_Terminate, MI_LMo_OAM_Tool, MI_LMo_Start, MI_LMo_Intermediate_Request, MI_LMo_Terminate, MI_DMo_OAM_Tool, MI_DMo_Start, MI_DMo_Intermediate_Request, MI_DMo_Terminate, MI_IDMo_OAM_Tool, MI_IDMo_Start, MI_IDMo_Terminate, and TI_TimeStampl.](8c3eb53c927f55acd19723cfcd0c43b6_img.jpg) + +RI\_CVM(D, CoS, DP), RI\_CVR(rTLV, TID) +RI\_LMMo(D, CoS, DP) +RI\_DMMo(D, CoS, DP) + +RI\_LMRo(TxFCf, RxFCf, TxFCb, RxFCb, CoS) +RI\_DMRo(TxTimeStampf, RxTimeStampf, +TxTimeStampb, RxTimeb, CoS) + +MTDe\_RP + +MI\_CV\_Series\_Result(REC, ERR, OO) +MI\_ITH\_Result(Sent) +MI\_LMo\_Result(N\_TF, N\_LF, F\_TF, F\_LF)[1...MLMo] +[1...MDMo] +MI\_CV\_Test\_Result(Sent, REC, REC, ERR, OO) +MI\_DMo\_Result(count, B\_FD[], F\_FD[], N\_FD())[1...MDMo] + +MTDe\_TT\_So\_MP + +MI\_GAL\_Enable +MI\_TTLVALUE +MI\_MEP\_ID + +MI\_CV\_OAM\_Tool +MI\_CV\_Series +(Target\_MEP/MIP\_ID, TTL, CoS, N, Length, Period) +MI\_CV\_Test(CoS, Pattern, Length, Period) +MI\_CV\_Terminate + +MI\_ITH\_OAM\_Tool +MI\_ITH\_Start(CoS, Pattern, Period) +MI\_ITH\_Terminate +MI\_LMo\_OAM\_Tool +MI\_LMo\_Start(P, Period)[1...MLMo] +MI\_LMo\_Intermediate\_Request[1...MLMo] +MI\_LMo\_Terminate[1...MLMo] +MI\_DMo\_OAM\_Tool +MI\_DMo\_Start(CoS, Period)[1...MDMo] +MI\_DMo\_Intermediate\_Request[1...MDMo] +MI\_DMo\_Terminate[1...MDMo] +MI\_IDMo\_OAM\_Tool +MI\_IDMo\_Start(CoS, Length, Period)[1...MIDMo] +MI\_IDMo\_Terminate[1...MIDMo] + +MTDe\_TT\_So\_TP + +TI\_TimeStampl + +Figure 9-10 – MTDe\_TT\_So process diagram. The diagram shows the internal components and data flows of the MTDe\_TT\_So process. At the top, inputs AI\_D and AI\_iPHB/oPHB enter a 'counter' block. The 'counter' block connects to a 'MEP on-demand G-ACh insertion' block. This block outputs PDU, TTL, Channel type, and PHB to an 'OAM PDU generation process' block. The 'OAM PDU generation process' block connects to an 'On-demand OAM source control' block. The 'On-demand OAM source control' block outputs TxFCI[] to the 'MEP on-demand G-ACh insertion' block. At the bottom, the 'MEP on-demand G-ACh insertion' block outputs CI\_D, CI\_oPHB, CI\_iPHB, and MT\_TCP. To the right of the diagram, a list of management interfaces is provided, categorized by MTDe\_RP, MTDe\_TT\_So\_MP, and MTDe\_TT\_So\_TP. The interfaces include RI\_CVM, RI\_LMMo, RI\_DMMo, RI\_LMRo, RI\_DMRo, MI\_CV\_Series\_Result, MI\_ITH\_Result, MI\_LMo\_Result, MI\_CV\_Test\_Result, MI\_DMo\_Result, MI\_GAL\_Enable, MI\_TTLVALUE, MI\_MEP\_ID, MI\_CV\_OAM\_Tool, MI\_CV\_Series, MI\_CV\_Test, MI\_CV\_Terminate, MI\_ITH\_OAM\_Tool, MI\_ITH\_Start, MI\_ITH\_Terminate, MI\_LMo\_OAM\_Tool, MI\_LMo\_Start, MI\_LMo\_Intermediate\_Request, MI\_LMo\_Terminate, MI\_DMo\_OAM\_Tool, MI\_DMo\_Start, MI\_DMo\_Intermediate\_Request, MI\_DMo\_Terminate, MI\_IDMo\_OAM\_Tool, MI\_IDMo\_Start, MI\_IDMo\_Terminate, and TI\_TimeStampl. + +Figure 9-10 – MTDe\_TT\_So process + +**G-ACh/GAL Insertion:** See clause 8.1 of [ITU-T G.8121]. + +##### **On-demand OAM Source Control** + +This process consists of the following sub-processes, in conjunction with the OAM PDU Generation process, as shown in Figure 9-11. These details are in clause 8.8 of [ITU-T G.8121.1]. + + + +The diagram illustrates the On-demand OAM Source Control process, showing the interaction between the OAM PDU generation process and various control blocks within the On-demand OAM control source process. + +**Control Blocks and their associated Management Information (MI) and Request Information (RI) messages:** + +- CVO control:** + - RI\_CVM(D, CoS, DP), RI\_CVR(rTLV, TID) + - MI\_CV\_Series(Target MEP/MIP\_ID, TTL, P, DP, N, Length, Period) + - MI\_CV\_Series\_Result(REC, ERR, OO) +- LMo control:** + - RI\_LMMo(TxFCf, RxFCf, TxFCb, RxFCb, CoS) + - MI\_LMo\_OAM\_Tool[1..MLMo] + - MI\_LMo\_Start(CoS, Period)[1..MLMo] + - MI\_LMo\_Terminate[1..MLMo] + - MI\_LMo\_Intermediate\_Request[1..MLMo, TxFC[]] + - MI\_LMo\_Result(N\_TF, N\_LF, F\_TF, F\_LF)[1..MLMo] +- DMo control:** + - RI\_DMMo(TxT.S.f, RxT.S.f, TxT.S.b, RxT.b, P, TestID) + - MI\_DMo\_OAM\_Tool[1..MDMo] + - MI\_DMo\_Start(CoS, Period)[1..MDMo] + - MI\_DMo\_Terminate[1..MDMo] + - MI\_DMo\_Intermediate\_Request[1..MDMo] + - MI\_DMo\_Result(count, B\_FD[], F\_FD[], N\_FD())[1..MDMo] +- IDMo control:** + - MI\_IDMo\_OAM\_Tool[1..MIDMo] + - MI\_IDMo\_Start(CoS, Period)[1..MIDMo] + - MI\_IDMo\_Terminate[1..MIDMo] +- TST (1TH) control:** + - MI\_1TH\_OAM\_Tool + - MI\_1TH\_Start(CoS, Pattern, Length, Period) + - MI\_1TH\_Terminate + - MI\_1DT\_Result(Sent) +- LMRo / DMRo:** + - RI\_LMMo(D, CoS, DP) + - RI\_DMMo(D, CoS, DP) + +**Other interactions:** + +- DMo/IDMo control:** TI\_TimeStamp1 +- OAM PDU generation process:** Interacts with the On-demand OAM control source process. + +G.8121.1-Y.1381.1(16)\_F9-11 + +Diagram of On-demand OAM Source Control process showing interactions between OAM PDU generation process and various control blocks (CVO, LMMo, DMMo, IDMo, IDT, LMMo/DMRo) with associated management information (MI) and request information (RI) messages. + +**Figure 9-11 – On-demand OAM Source Control process** + +On-demand OAM PDU Generation process: See clause 8.8 of [ITU-T G.8121]. + +**Counter:** See clause 8.8.5.7 of [ITU-T G.8121.1]. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.4.1.2 MT diagnostic sink function for MEP (MTDe\_TT\_Sk) + +##### Symbol + +The MTDe\_TT\_Sk function symbol is shown in Figure 9-12. + + + +Diagram of the MTDe\_TT\_Sk symbol. It is a triangle pointing downwards. The top vertex is labeled MT\_AP. The left vertex is labeled MT\_TT\_Sk\_MP. The right vertex is labeled MT\_RP. The bottom vertex is labeled MT\_TCP. Below the triangle is the text G.8121.1-Y.1381.1(13)\_F9-12. + +Figure 9-12 – MTDe\_TT\_Sk symbol + +##### Interfaces + +Table 9-4 – MTDe\_TT\_Sk interfaces + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MT_TCP:
MT_CI_D
MT_CI_iPHB
MT_CI_oPHB
MT_CI_LStack
MTDe_TT_Sk_MP:
MTDe_TT_Sk_MI_GAL_Enable
MTDe_TT_Sk_MI_MEP_ID
MTDe_TT_Sk_MI_CV_OAM_Tool
MTDe_TT_Sk_MI_1TH_OAM_Tool
MTDe_TT_Sk_MI_1TH_Start(Period)
MTDe_TT_Sk_MI_1TH_Terminate
MTDe_TT_Sk_MI_LMo_OAM_Tool[1...M LMo ]
MTDe_TT_Sk_MI_DMo_OAM_Tool[1...M DMo ]
MTDe_TT_Sk_MI_1DMo_OAM_Tool[1...M 1DMo ]
MTDe_TT_Sk_MI_1DMo_Start(CoS)[1...M 1DMo ]
MTDe_TT_Sk_MI_1DMo_Intermediate_Request[1...M LMo ]
MTDe_TT_Sk_MI_1DMo_Terminate[1...M 1DMo ]
MTDe_TP:
MTDe_TT_Sk_TI_TimeStamp1 | MTDe_AP:
MTDe_AI_D
MTDe_AI_oPHB
MTDe_AI_iPHB
MTDe_AI_LStack
MTDe_RP:
MTDe_RI_CVM(D, CoS, DP)
MTDe_RI_CVR(rTLV, TID)
MTDe_RI_LMMo(D, CoS, DP)
MTDe_RI_DMMo(D, CoS, DP)
MTDe_RI_LMRo(TxFCf,RxFCf,TxFCb,RxFCb,CoS)
MTDe_RI_DMRo(TxTimeStampf,RxTimeStampf,TxTimeStampb,RxTimeb,CoS,TestID)
MTDe_TT_Sk_MP:
MTDe_TT_Sk_MI_1TH_Result(REC,CRC,BER,O)
MTDe_TT_Sk_MI_1DMo_Result(count,N_FD[])[1...M DMo ] | + +##### Processes + +The processes associated with the MTDe\_TT\_Sk function are as depicted in Figure 9-13. + +![Figure 9-13 – MTDe_TT_Sk process diagram. This block diagram shows the internal architecture of the MTDe_TT_Sk process. On the left, various management interfaces are listed: RI_CVM(D, CoS, DP), RI_LMMo(D, CoS, DP), RI_DMMo(D, CoS, DP), RI_LMRo(TxFcf, RxFcf, TxFCb, RxFCb, CoS), RI_DMRo(TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, CoS, TestID), RI_CVR(fTLV, TID), MI_ITH_Result(REC, CRC, BER, OO), MI_IDMo_Result(count, N_FD[])[1..M_DMo], MI_MEP_ID, MI_CV_OAM_Tool, MI_ITH_OAM_Tool, MI_ITH_Start(Pattern, Length, Period), MI_ITH_Terminate, MI_LMo_OAM_Tool, MI_DMo_OAM_Tool, MI_IDMo_OAM_Tool, MI_IDMo_Start(Test_ID)[1..M_IDMo], MI_IDMo_Terminate[1..M_IDMo], MI_SLo_OAM_Tool, MI_GAL_Enable, and TI_TimeStamp. These interfaces connect to three main internal blocks: 'On-demand OAM sink control', 'OAM PDU reception', and 'MEP on-demand G-Ach extraction'. The 'OAM PDU reception' block connects to an 'OAM' block, which in turn connects to a 'Counter' block. The 'Counter' block has inputs for 'RxFCI[]' and 'non OAM'. Above the 'Counter' block are four output interfaces: AI_iPHB, AI_oPHB, AI_D, and AI_LStack. Below the 'MEP on-demand G-Ach extraction' block are three output interfaces: CI_iPHB, CI_D, and CI_LStack, with CI_oPHB also shown. The entire process is labeled MTDe_AP at the top and MT_TCP at the bottom, with the reference G.8121.1-Y.1381.1(16)_F9-13.](32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg) + +Figure 9-13 – MTDe\_TT\_Sk process diagram. This block diagram shows the internal architecture of the MTDe\_TT\_Sk process. On the left, various management interfaces are listed: RI\_CVM(D, CoS, DP), RI\_LMMo(D, CoS, DP), RI\_DMMo(D, CoS, DP), RI\_LMRo(TxFcf, RxFcf, TxFCb, RxFCb, CoS), RI\_DMRo(TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, CoS, TestID), RI\_CVR(fTLV, TID), MI\_ITH\_Result(REC, CRC, BER, OO), MI\_IDMo\_Result(count, N\_FD[])[1..M\_DMo], MI\_MEP\_ID, MI\_CV\_OAM\_Tool, MI\_ITH\_OAM\_Tool, MI\_ITH\_Start(Pattern, Length, Period), MI\_ITH\_Terminate, MI\_LMo\_OAM\_Tool, MI\_DMo\_OAM\_Tool, MI\_IDMo\_OAM\_Tool, MI\_IDMo\_Start(Test\_ID)[1..M\_IDMo], MI\_IDMo\_Terminate[1..M\_IDMo], MI\_SLo\_OAM\_Tool, MI\_GAL\_Enable, and TI\_TimeStamp. These interfaces connect to three main internal blocks: 'On-demand OAM sink control', 'OAM PDU reception', and 'MEP on-demand G-Ach extraction'. The 'OAM PDU reception' block connects to an 'OAM' block, which in turn connects to a 'Counter' block. The 'Counter' block has inputs for 'RxFCI[]' and 'non OAM'. Above the 'Counter' block are four output interfaces: AI\_iPHB, AI\_oPHB, AI\_D, and AI\_LStack. Below the 'MEP on-demand G-Ach extraction' block are three output interfaces: CI\_iPHB, CI\_D, and CI\_LStack, with CI\_oPHB also shown. The entire process is labeled MTDe\_AP at the top and MT\_TCP at the bottom, with the reference G.8121.1-Y.1381.1(16)\_F9-13. + +Figure 9-13 – MTDe\_TT\_Sk process + +**G-ACh/GAL Extraction:** See clause 8.1 of [ITU-T G.8121]. + +**On-demand OAM PDU Reception:** See clause 8.8 of [ITU-T G.8121]. + +**On-demand OAM Sink Control:** This process consists of following sub-processes, in conjunction with OAM PDU Generation process, as shown Figure 9-13. These details are in clause 8.8. + +**Counter:** See clause 8.8.5.7 of [ITU-T G.8121.1]. + +![Figure 9-14 – On-Demand OAM Sink Control process diagram. The diagram shows the flow of OAM PDUs from right to left through various control and demux blocks. On the right, a vertical bar labeled 'OAM PDU reception' contains labels LMMo, DMMo, oCV, LMRo, DMRo, IDMo, and IDT. Arrows from these labels point to corresponding blocks: 'CVO control', 'LMRo demux', 'DMRo demux', 'IDMo control' (containing 'IDMo demux'), and 'TST (IDT) control'. A dashed box labeled 'On-demand OAM control process' encloses the 'CVO control', 'LMRo demux', 'DMRo demux', and 'IDMo control' blocks. Input data on the left includes RI_LMMo(D, CoS, DP), RI_DMMo(D, CoS, DP), RI_CVM(D, CoS, DP), RI_CVR(rTLV, TID), MI_MEG_ID, MI_PeerMEP_ID, MI_CV_OAM_Tool, RI_LMRo(TxFCf, RxFCf, TxFCb, RxFCI, CoS), MI_LMo_OAM_Tool, RxFC[], RI_DMRo(TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, CoS, TestID), MI_DMo_OAM_Tool, MI_IDMo_Start(TestID)[1..M_IDMo], MI_IDMo_Terminate[1..M_IDMo], MI_IDMo_Result(count, N_FD[])[1..M_IDMo], MI_IDMo_OAM_Tool, MI_ITH_Result(REC, CRC, BER, OO), MI_ITH_Start(Period), MI_ITH_Terminate, and MI_ITH_OAM_Tool. Output data on the right includes RI_LMMo, RI_DMMo, and MI_ITH_Start(Period). A reference code G.8121.1-Y.1381.1(16)_F9-14 is at the bottom right.](c6212a3b14736d6a8c81ace75ae94ccf_img.jpg) + +Figure 9-14 – On-Demand OAM Sink Control process diagram. The diagram shows the flow of OAM PDUs from right to left through various control and demux blocks. On the right, a vertical bar labeled 'OAM PDU reception' contains labels LMMo, DMMo, oCV, LMRo, DMRo, IDMo, and IDT. Arrows from these labels point to corresponding blocks: 'CVO control', 'LMRo demux', 'DMRo demux', 'IDMo control' (containing 'IDMo demux'), and 'TST (IDT) control'. A dashed box labeled 'On-demand OAM control process' encloses the 'CVO control', 'LMRo demux', 'DMRo demux', and 'IDMo control' blocks. Input data on the left includes RI\_LMMo(D, CoS, DP), RI\_DMMo(D, CoS, DP), RI\_CVM(D, CoS, DP), RI\_CVR(rTLV, TID), MI\_MEG\_ID, MI\_PeerMEP\_ID, MI\_CV\_OAM\_Tool, RI\_LMRo(TxFCf, RxFCf, TxFCb, RxFCI, CoS), MI\_LMo\_OAM\_Tool, RxFC[], RI\_DMRo(TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, CoS, TestID), MI\_DMo\_OAM\_Tool, MI\_IDMo\_Start(TestID)[1..M\_IDMo], MI\_IDMo\_Terminate[1..M\_IDMo], MI\_IDMo\_Result(count, N\_FD[])[1..M\_IDMo], MI\_IDMo\_OAM\_Tool, MI\_ITH\_Result(REC, CRC, BER, OO), MI\_ITH\_Start(Period), MI\_ITH\_Terminate, and MI\_ITH\_OAM\_Tool. Output data on the right includes RI\_LMMo, RI\_DMMo, and MI\_ITH\_Start(Period). A reference code G.8121.1-Y.1381.1(16)\_F9-14 is at the bottom right. + +**Figure 9-14 – On-Demand OAM Sink Control process** + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 9.4.2 MT diagnostic functions for MIP (MTDi) + +#### 9.4.2.1 MT diagnostic trail termination functions for MIP + +The MTDi/MT adaptation function is an empty function; it is included to satisfy the modelling rules. + +The bidirectional MTD/MT adaptation function is performed by a co-located pair of MTDi/MT adaptation source (MTDi/MT\_A\_So) and sink (MTDi/MT\_A\_Sk) functions. + +##### 9.4.2.1.1 MT Diagnostic trail termination source function for MIP (MTDi\_TT\_So) + +###### Symbol + +The MTDi\_TT\_So function symbol is shown in Figure 9-15. + + + +G.8121.1-Y.1381.1(13)\_F9-15 + +MTDi\_TT\_So symbol diagram showing a central triangle labeled MTDi with four interfaces: MTDi\_AP (top), MTDi\_TT\_So\_MP (left), MTDi\_RP (right), and MTDi\_TCP (bottom). + +**Figure 9-15 – MTDi\_TT\_So symbol** + +###### **Interfaces** + +**Table 9-5 – MTDi\_TT\_So interfaces** + +| Inputs | Outputs | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| +| MTDi_AP
MT_AI_D
MT_AI_iPHB
MT_AI_oPHB
MT_AI_LStack
MTDi_RP
MTDi_RI_CV_Info (D, CoS, DP)
MTDi_TT_So_MP
MTDi_TT_So_MI_GAL_Enable
MTDi_TT_So_MI_TTLVALUE
MTDi_TT_So_MI_MIP_ID
MTDi_TT_So_MI_CV_OAM_Tool | MTDi_TCP
MT_CI_D,
MT_CI_iPHB,
MT_CI_oPHB,
MT_CI_LStack | + +###### **Processes** + +The processes associated with the MTDi\_TT\_So function are as depicted in Figure 9-16. + + + +G.8121.1-Y.1381.1(13)\_F9-16 + +MTDi\_TT\_So process diagram showing internal components: On-demand OAM source control, On-demand OAM PDU generation, and OAM (MEP on-demand OAM G.A ch insertion). It shows data flow from MTDi\_AP (AI\_D/iPHB/oPHB, AI\_LStack) through Data and OAM blocks to MTDi\_TCP (CI\_D/iPHB/oPHB, CI\_LStack). Control inputs from MTDi\_TT\_So\_MP and MTDi\_RP are shown on the left. + +**Figure 9-16 – MTDi\_TT\_So process** + +**MIP OAM insertion:** See clause 9.4.2.1.1 of [ITU-T G.8121]. + +**On-demand OAM PDU Generation:** See clause 9.4.2.1.1 of [ITU-T G.8121]. + +**On-demand OAM Source Control:** This process consists of oCV and RT sub-processes. These details are in clause 8.8. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +##### 9.4.2.1.2 MT diagnostic trail termination sink function for MIP (MTDi\_TT\_Sk) + +###### Symbol + +The MTDi\_TT\_Sk function symbol is shown in Figure 9-17. + + + +Figure 9-17 – MTDi\_TT\_Sk symbol. The diagram shows a central triangle labeled 'MTDi'. Four arrows point to it: 'MTDi\_TT\_Sk\_MP' from the left, 'MTDi\_TCP' from the bottom, 'MTDi\_AP' from the top, and 'MTDi\_RP' from the right. Below the triangle is the text 'G.8121.1-Y.1381.1(16)\_F9-17'. + +**Figure 9-17 – MTDi\_TT\_Sk symbol** + +###### Interfaces + +**Table 9-6 – MTDi\_TT\_Sk interfaces** + +| Inputs | Outputs | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| MTDi_TCP
MT_CI_D
MT_CI_iPHB
MT_CI_oPHB
MT_CI_LStack
MTDi_TT_Sk_MP
MTDi_TT_Sk_MI_GAL_Enable
MTDi_TT_Sk_MI_MIP_ID
MTDi_TT_Sk_MI_CV_OAM_Tool | MTDi_AP
MT_AI_D
MT_AI_iPHB
MT_AI_oPHB
MT_AI_LStack
MTDi_RP
MTDi_RI_CV_Info (D, CoS, DP) | + +###### Processes + +The processes associated with the MTDi\_TT\_Sk function are as depicted in Figure 9-18. + + + +Figure 9-18 – MTDi\_TT\_Sk process diagram. The diagram shows the internal structure of the MTDi\_TT\_Sk process. On the left, external interfaces are labeled: MTDi\_TT\_Sk\_MP (with MI\_GAL\_Enable, MI\_MIP\_ID, MI\_CV\_OAM\_Tool) and MTDi\_RP (with RI\_CV\_Info(D, CoS, DP)). The process contains three main sub-blocks: 'On-demand OAM sink control', 'OAM PDU reception', and 'MIP on-demand OAM G-Ach extraction'. The 'On-demand OAM sink control' block receives inputs from MI\_GAL\_Enable, MI\_MIP\_ID, and MI\_CV\_OAM\_Tool, and sends RI\_CV\_Info(D, CoS, DP) to the MTDi\_RP interface. It also connects to the 'OAM PDU reception' block. The 'OAM PDU reception' block receives PDU, PHB, and Channel type inputs from the 'MIP on-demand OAM G-Ach extraction' block and sends data to the 'On-demand OAM sink control' block. The 'MIP on-demand OAM G-Ach extraction' block contains a 'Data' block and an 'OAM' block. It receives inputs from the AI\_D/iPHB/oPHB/LStack (top) and CI\_D/iPHB/oPHB/LStack (bottom) interfaces. The diagram is labeled with MTDi\_AP at the top and MT\_TCP at the bottom, with the reference G.8121.1-Y.1381.1(13)\_F9-18. + +Figure 9-18 – MTDi\_TT\_Sk process + +**MIP OAM extraction:** See clause 9.4.2.1.2 of [ITU-T G.8121]. + +**On-demand OAM PDU Reception:** See clause 9.4.2.1.2 of [ITU-T G.8121]. + +###### On-demand OAM Sink Control + +This process consists of oCV sub-processes. These details are in clause 8.8. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.4.2.2 MTDi to MT Adaptation functions (MTDi/MT\_A) + +See clause 9.4.2.2 of [ITU-T G.8121]. + +# 10 MPLS-TP to Non-MPLS-TP client adaptation functions + +These atomic functions, except the MPLS-TP to ETH adaptation function, are defined in clause 10 of [ITU-T G.8121]. + +## 10.1 MPLS-TP to ETH adaptation function (MT/ETH\_A) + +### 10.1.1 MPLS-TP to ETH adaptation source function (MT/ETH\_A\_So) + +This function maps the ETH\_CI information for transport in a MT\_AI signal. + +The information flow and processing of the MT/ETH\_A\_So function is defined with reference to Figure 10-1. + +#### Symbol + + + +Diagram of the MT/ETH\_A\_So function symbol. It is a yellow trapezoid. An arrow labeled 'ETH\_CI' points down to the top of the trapezoid. An arrow labeled 'MT/ETH\_A\_So\_MI' points from the left to the left side of the trapezoid. An arrow labeled 'MT\_AI' points down from the bottom of the trapezoid. To the right of the bottom arrow is the text 'G.8121.1-Y.1381.1(18)\_F10-1'. + +**Figure 10-1 – MT/ETH\_A\_So function** + +#### Interfaces + +The MT/ETH\_A\_So interfaces are described in Table 10-1. + +**Table 10-1 – MT/ETH\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| ETH_CI:
ETH_CI_Data
ETH_CI_P
ETH_CI_DE
MT/ETH_A_So_MP:
MT/ETH_A_So_MI_Active
MT/ETH_A_So_MI_AdminState
MT/ETH_A_So_MI_FCSEnable
MT/ETH_A_So_MI_CWEnable
MT/ETH_A_So_MI_SQUse
MT/ETH_A_So_MI_PRI2CoSMapping
MT/ETH_A_So_MI_GAL_Enable
MT/ETH_A_So_MI_CSF_OAM_Tool
MT/ETH_A_So_MI_CSF_Period
MT/ETH_A_So_MI_CSF_CoS
MT/ETH_A_So_MI_CSFdciEnable
MT/ETH_A_So_MI_CSF_Enable
MT/ETH_A_So_MI_CSFrdifdiEnable
MT/ETH_A_So_MI_MEP_MAC*
MT/ETH_A_So_MI_Client_MEL*
MT/ETH_A_So_MI_LCK_Period*
MT/ETH_A_So_MI_LCK_Pri*
MT/ETH_A_So_MI_MEL*
* ETH OAM related | MT_AP:
MT_AI_Data
MT_AI_PHB | + +#### Processes + +The processes associated with the MT/ETH\_A\_So function are as depicted in Figure 10-2. + + + +Figure 10-2 – MT/ETH\_A\_So process diagram. This flowchart illustrates the data processing pipeline for MT/ETH\_A\_So. The process starts with two inputs: ETH\_CSF\_SSF and ETH\_CI. ETH\_CI is processed through a series of blocks: 'LCK generate' (receiving D, P, DE and MI parameters: MI\_Active, MI\_MEP\_MAC, MI\_Client\_MEL, MI\_LCK\_Period, MI\_LCK\_Pri), 'Normal Lock Selector' (receiving D, P, DE and MI\_Admin\_State), 'OAM MEL filter' (receiving D, P, DE and MI\_MEL), '802.3 MAC FCS' (receiving D, P, DE and MI\_FCSenable), 'QoS mapping' (receiving D, P, DE and MI\_PRI2CoSMapping), 'CW insertion' (receiving D, PHB and MI\_CWEnable, MI\_SQUse), and 'Insert S bit' (receiving D, PHB). The output of 'Insert S bit' and a signal from 'Consequent actions' (receiving MI\_CSF\_Enable, MI\_CSFrdifdiEnable and sending aCSF-RDI, aCSF-FDI, aCSF-LOS) are inputs to the 'CSF insert' block. 'CSF insert' also receives MI parameters: MI\_GAL\_Enable, MI\_CSF\_OAM\_Tool, MI\_CSF\_OAM\_Period, MI\_CSF\_OAM\_CoS, and MI\_CSF\_dciEnable. The final output is MT\_AI, which is the result of D and PHB processing in the 'CSF insert' block. A reference code G.8121.1-Y.1381.1(18)\_F10-2 is shown at the bottom right. + +Figure 10-2 – MT/ETH\_A\_So process diagram + +##### CSF insert process: + +As defined in clause 8.7.3. + +Other processes without consequent actions in Figure 10-2 are defined in clause 10.1.1 of [ITU-T G.8121]. + +##### Defects + +None. + +###### Consequent actions + +$aCSF-LOS \leftarrow CI\_SSF \text{ and } MI\_CSF\_Enable$ + +$aCSF-RDI \leftarrow CI\_SSFrdfi \text{ and } MI\_CSFrdifdiEnable \text{ and } MI\_CSF\_Enable$ + +$aCSF-FDI \leftarrow CI\_SSFfdi \text{ and } MI\_CSFrdifdiEnable \text{ and } MI\_CSF\_Enable$ + +##### Defect correlations + +None. + +##### Performance monitoring + +None. + +### 10.1.2 MPLS-TP to ETH adaptation sink function (MT/ETH\_A\_Sk) + +This function extracts the ETH\_CI information from an MT\_AI signal. + +The information flow and processing of the MT/ETH\_A\_Sk function is defined with reference to Figure 10-3. + +#### Symbol + + + +Figure 10-3 – MT/ETH\_A\_Sk function symbol diagram. A yellow trapezoidal block labeled 'MT/ETH\_A\_Sk' has an input arrow labeled 'MT\_AI' pointing into its bottom vertex. An output arrow labeled 'ETH\_CI' points out of its top vertex. A double-headed arrow labeled 'MT/ETH\_A\_Sk\_MI' is connected to its right side. A small text label 'G.812.1.1-Y.1381.1(18)\_F10-3' is located to the right of the input arrow. + +Figure 10-3 – MT/ETH\_A\_Sk function + +##### Interfaces + +The MT/ETH\_A\_Sk interfaces are described in Table 10-2. + +Table 10-2 – MT/ETH\_A\_Sk Inputs and Outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Each MT_AP:
MT_AI_Data
MT_AI_PHB
MT_AI_TSF
MT_AI_AIS
MT/ETH_A_Sk_MP:
MT/ETH_A_Sk_MI_Active
MT/ETH_A_Sk_MI_FCSEnable
MT/ETH_A_Sk_MI_CWEnable
MT/ETH_A_Sk_MI_SQUse
MT/ETH_A_Sk_MI_GAL_Enable
MT/ETH_A_Sk_MI_CoS2PRIMapping
MT/ETH_A_Sk_MI_GAL_Enable
MT/ETH_A_Sk_MI_CSF_OAM_Tool
MT/ETH_A_Sk_MI_CSF_Reported
MT/ETH_A_Sk_MI_CSFrdifdiEnable
MT/ETH_A_Sk_MI_MEL *
MT/ETH_A_Sk_MI_Admin_State
MT/ETH_A_Sk_MI_LCK_Period *
MT/ETH_A_Sk_MI_LCK_Pri *
MT/ETH_A_Sk_MI_Client_MEL *
MT/ETH_A_Sk_MI_MEP_MAC *
MT/ETH_A_Sk_MI_AIS_Pri *
MT/ETH_A_Sk_MI_AIS_Period *
* ETH OAM related | ETH_FP:
ETH_CI_Data
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF
MT/ETH_A_Sk_MP:
MT/ETH_A_MI_pFCSErrors
MT/ETH_A_Sk_MI_eCSF | + +##### Processes + +The processes associated with the MT/ETH\_A\_Sk function are as depicted in Figure 10-4. + + + +Figure 10-4 – MT/ETH\_A\_Sk process diagram. This is a complex block diagram showing the data flow and control logic for the MT/ETH\_A\_Sk function. The diagram is organized vertically. At the top, an 'ETH\_CI' input is shown with 'D', 'P', and 'DE' sub-ports. Below it, a 'Selector' block has 'Normal' and 'Lock' options, controlled by 'MI\_Admin\_State'. A 'LCK generate' block is connected to the 'Lock' option and receives inputs from 'MI\_LCK\_Period', 'MI\_LCK\_Pri', 'MI\_MEP\_MAC', and 'MI\_Client\_MEL'. Below the Selector is an 'AIS insert' block, receiving 'aSSF' and 'aAIS' inputs and controlled by 'MI\_AIS\_Period' and 'MI\_AIS\_Pri'. To the left, a 'Consequent actions' block receives 'MI\_CSFrdifdiEnable' and outputs 'aSSF' and 'aAIS'. Below 'AIS insert' is an 'OAM MEL filter' block, controlled by 'MI\_MEL'. Below that is an '802.3 MAC Frm Chk' block, controlled by 'MI\_FCSEnable' and outputting 'pFCSErrors'. Below that is a 'QoS mapping' block, controlled by 'MI\_PSC2CoSMapping'. Below that is a 'CW extraction' block, controlled by 'MI\_CWEnable' and 'MI\_SQUse'. Below that is an 'Extract S bit' block, controlled by 'PHB'. Below that is a 'CSF extract' block, controlled by 'MI\_GAL\_Enable' and 'MI\_CSF\_Tool', and receiving 'PHB' and 'CSF' inputs. To the left of 'CSF extract' are 'Defect generation' and 'Defect correlations' blocks, which receive 'dCSF' and output 'MI\_cCSF' and 'MI\_CSF\_Reported'. Below 'CSF extract' is a 'G-ACH filter' block, controlled by 'PHB' and receiving 'D', 'AIS', and 'TSF' inputs. At the bottom, 'MT\_AI' is shown with 'D', 'P', and 'DE' sub-ports. Various 'D', 'P', and 'DE' labels are placed throughout the diagram to indicate data, priority, and defect/enable signals. A reference code 'G.8121.1-Y.1381.1(18)\_F10-4' is in the bottom right corner. + +Figure 10-4 – MT/ETH\_A\_Sk process diagram + +##### CSF extract process: + +As defined in clause 8.7.3. + +Other processes without consequent actions, Defect Correlations, and Defect Generation in Figure 10-4 are defined in clause 10.1.1 of [ITU-T G.8121]. + +##### Defects + +None. + +###### **Consequent actions** + +The function shall perform the following consequent actions: + +$aSSF \leftarrow (AI\_TSF \text{ or } dCSF-LOS) \text{ and } (not \ MI\_Admin\_State == \text{Locked})$ + +$aSSFrdfi \leftarrow dCSF-RDI \text{ and } MI\_CSFrdfiEnable$ + +$aSSFfdi \leftarrow dCSF-FDI \text{ and } MI\_CSFfdiEnable$ + +$aAIS \leftarrow AI\_AIS$ + +##### **Defect correlations** + +$cCSF \leftarrow (dCSF-LOS \text{ or } dCSF-RDI \text{ or } dCSF-FDI) \text{ and } (not \ AI\_TSF) \text{ and } MI\_CSF\_Reported$ + +##### **Performance monitoring** + +None. + +# **11 Non-MPLS-TP Server to MPLS-TP adaptation functions** + +These atomic functions are defined in clause 11 of [ITU-T G.8121]. They use the OAM protocol specific AIS insertion process and LCK generation process as defined in clauses 8.6.2 and 8.6.3. + +# Appendix I + +## Counting OAM packets + +(This appendix does not form an integral part of this Recommendation.) + +Table I.1 provides Counting OAM Packets for proactive Dual-Ended LM. The counter process is described in clause 8.8.1.4. + +**Table I.1 – Counting OAM Packets for proactive Dual-Ended LM** + +| OAM packet type | Counted or not counted | Atomic function that receives the PDU | +|-----------------|--------------------------|---------------------------------------| +| APS | Counted | MT/MT_A_Sk
Or MT/MTp_A_Sk | +| CCM | Not counted | MT_TT_Sk | +| LBM, LBR | Not counted | MTDe_TT_Sk | +| TST | Not counted | MTDe_FT_Sk | +| AIS | Not Specified (see Note) | MT/MT_A_Sk | +| LCK | Not Specified (see Note) | MT/MT_A_Sk | +| DMM, DMR, 1DM | Not counted | MTDe_TT_Sk or MT_TT_Sk | +| LMM, LMR | Not counted | MTDe_TT_Sk or MT_TT_Sk | + +NOTE – As OAM frames for AIS and LCK are only sent in the defect conditions where the result of loss measurements is invalid, it is unnecessary to count these frames. + +Table I.2 provides counting OAM packets for both proactive and on-demand single-ended LM. The counter process is described in clause 8.8.4.7. + +**Table I.2 – Counting OAM packets for single-ended LM** + +| OAM frame OpCode | Counted or not counted | Atomic function that receives the PDU | +|------------------|--------------------------|---------------------------------------| +| APS | Counted | MT/MT_A_Sk
Or MT/MTp_A_Sk | +| CCM | Counted | MT_TT_Sk | +| LBM, LBR, | Not counted | MTDe_TT_Sk | +| TST | Not counted | MTDe_FT_Sk | +| AIS | Not Specified (see Note) | MT/MT_A_Sk | +| LCK | Not Specified (see Note) | MT/MT_A_Sk | +| DMM, DMR, 1DM | Not counted | MTDe_TT_Sk or MT_TT_Sk | +| LMM, LMR | Not counted | MTDe_TT_Sk or MT_TT_Sk | + +NOTE – As OAM frames for AIS and LCK are only sent in the defect conditions where the result of loss measurements is invalid, it is unnecessary to count these frames. + +# Appendix II + +## SDL descriptions + +(This appendix does not form an integral part of this Recommendation.) + +In this Recommendation, detailed characteristics of equipment functional blocks are described with SDL diagrams specified in [b-ITU-T Z.100]. The SDL diagrams use the following conventions. + + + +| | | | | +|--|-----------------|--|------------------| +| | Procedure start | | Decision | +| | Procedure stop | | Task | +| | State | | Output | +| | Input | | Procedure call | +| | Label/connector | | Procedure return | + +G.8121.1-Y.1381.1(16)\_FII.1 + +A grid of ten SDL symbols with their labels. The symbols are: Procedure start, Procedure stop, State, Input, Label/connector, Decision, Task, Output, Procedure call, and Procedure return. Procedure start symbol: a horizontal stadium shape (rounded rectangle). Decision symbol: a diamond shape. Procedure stop symbol: a large X shape. Task symbol: a simple rectangle. State symbol: a horizontal stadium shape with vertical lines near the ends. Output symbol: a rectangle with a concave right side. Input symbol: a rectangle with a convex left side. Procedure call symbol: a rectangle with double vertical lines on the left and right sides. Label/connector symbol: a simple circle. Procedure return symbol: a circle with an X inside. + +**Figure II.1 – SDL symbols** + +# Bibliography + +- [b-ITU-T Z.100] Recommendation ITU-T Z.100 (2011), *Specification and Description Language – Overview of SDL-2010*. + +# 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.8152-202401-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0bb9e8e8955c49f1a0fef0af1c9dd5660821d41 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:740c74fdfd6f25b53c4145c459c3c72339672b6c30070b6ebb0ac0b18fdfe648 +size 32353 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/0958fb9f1140d3b2a1dcadbbe544079b_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/0958fb9f1140d3b2a1dcadbbe544079b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75b85c3715ed2225b64ef5ad2b6ca50521afd9c8 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/0958fb9f1140d3b2a1dcadbbe544079b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbb4902692c15798e993fb74b565d0020a4f95f04cc63ba82ed93fc9c8232954 +size 13282 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/0f26e70157bd4c45f825795cdcd20fbd_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/0f26e70157bd4c45f825795cdcd20fbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f40a207efc22b910a6677b240faedd7eaf49ab70 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/0f26e70157bd4c45f825795cdcd20fbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:528ed9abc265228bff1106e9f3d64c83dbeb18f8108f37517ec4d97ec2fab350 +size 75758 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b784c855593d88678c3c0160a68c37340ad4676 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:936b54df55f9927029a4caeec069ab9921a5b82d95d9c0a3caa584a8e7f09feb +size 32034 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5acfc61b4e491192c99a4ee15095b00a2e85f0a --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c43e7823a651679d415da685564fb82cbabb5fae813cd02b9fa08aeb9476719 +size 29433 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2ed6c375c18601ab600e48c907ed3b14f5ff0ca --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0fbddc4da5ba54f9726a7ab90870b77fdb5d151695144e0a4b2b33aa84071d8 +size 16919 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/1b9ef0ed601d44177c2110acd926e94e_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/1b9ef0ed601d44177c2110acd926e94e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13a55422b6016f9cb7e28949dcdffea6e5f82ae3 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/1b9ef0ed601d44177c2110acd926e94e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:749f8dc5c41f6adbfddc8285cb35855651e31968d9d7a285d66b6117fff5d3d7 +size 11776 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45263c73610acd85657b9854b15df30edbc21fd4 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c9243f350d2b5b3a2f1bef488cf4e46e5255a0368a0639bb14adcbbaf65c721 +size 60231 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/1dcae6d69e49d4ae3ed49bf49e9c143e_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/1dcae6d69e49d4ae3ed49bf49e9c143e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8265dc47ba45b68d05e4c0dea4059953a67909d --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/1dcae6d69e49d4ae3ed49bf49e9c143e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70c479dc71b402ee5382cc85f4ad2727a0a214368338f3e67ab64e25ffc4cf02 +size 11287 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfaf8d005785548a220de69a7a9b27ab07cd824f --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f54b7ea704bc5bf4a8b33bff2434132ed496abe649548c0633051bd1cbb29fd2 +size 41440 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8b4dd878caf0b6ba5ea114130e52c95234cd72f --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82facd9fbda6b655c7348c214b0032999dd3e7589bf16ce0e2011b3ce0b42d73 +size 32483 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e485e77c08a0b0da7f64472c4df989fa22a488a2 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cb080ac273c2aa628278edc1bcb5892f7c7d6522aec3b674abdfeca10afbedf +size 40039 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99422cff92149969755ec44d9540b48e48fd0964 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54e6bac03237c3eed514e70b96d65ce3117acd93da871706697314b424ddd717 +size 25466 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..173ba641137d5ed347324891c130d76f1ba72dce --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d5a0d5de627eedd635dee1167cd1eead97f199c0222ec498d3b2a4ab678375b +size 22537 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/52f53aebe3bf200bcd114a1e95e3b8d9_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/52f53aebe3bf200bcd114a1e95e3b8d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..429f522612951c7c6c0094159702794486aabfc1 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/52f53aebe3bf200bcd114a1e95e3b8d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab15ba6a6183e96999cfd2e473fe234e60862ce6c82c9e9a5f91025723939d73 +size 12950 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b30782910efe7eb6e700ac2452130e7ac330ac3b --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e0b420ee5c939e7fa6b00ab8032313ee284966e826204b82a57f01c615d6802 +size 159801 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/5ec1c7f2052fd78f78e28d9c5886a466_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/5ec1c7f2052fd78f78e28d9c5886a466_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0c1025c3f2b0ac4d0402b440e1524c2b91787cf --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/5ec1c7f2052fd78f78e28d9c5886a466_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb21640b0c18c78ab47c376d616d0881ec2054b95dc703a81c2b58827e8054f6 +size 11466 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8e91ce62a25b460604e0d5a650a9e6e5434acba --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c462d6ee8fa78df77125556500e4eee2a2b8fabf914d7f6dde431963e0f426d2 +size 166365 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7303ca0a0a6e9dd0af861b1c21a418b692d8073 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61e166ecb634c52731495ce97b037f4970967dab28553e9ee6820f873786f351 +size 96017 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/80f019590b32ded8c1ec459a936444e1_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/80f019590b32ded8c1ec459a936444e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20989b7292cc16e8401fc396e75f959b01eed1cf --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/80f019590b32ded8c1ec459a936444e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e898338e6a65e002b51fc4b7757b3a8cb0e63fb760013e67c85d46d9018ecf7 +size 12299 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a017f869dde23b853c9ba958e30d213c3993cba0 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48f1539bc81203a8396c9437bdd3f7dac72d3f34e6f26bff42f08206251e9913 +size 32078 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..def289ffe2570036a572f52ffa6f1e0b7f1dece1 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd384c3ea8fc318ef3bb6acb48c9c9cf42e2bb971910abef2d68f7509b2a5c7b +size 25934 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ede1a6213089c0910f6f43af29dd80e92e2d4a3 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03e3f175d096c30b63d5a7c5b4f77694b750e952a0033ccbcda0c7debf7158fb +size 92273 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/8fbfbb6bcb1e1ec27bf520869d3f1f64_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/8fbfbb6bcb1e1ec27bf520869d3f1f64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35284bc9b6ea31656550fd816593b9e1b1aabde6 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/8fbfbb6bcb1e1ec27bf520869d3f1f64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7881d244a4c23360ba43991edf25a9caadb39c0bebc7a35f87fdeb2193a4d6fa +size 10383 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/98247139ff59efc152aa64d668271fba_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/98247139ff59efc152aa64d668271fba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..784ce2873b7e91c3493cec74b6597235057d0ca2 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/98247139ff59efc152aa64d668271fba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e42628f745e632bc7d070f804ef28eedfd9c0910b2a1de1033f5837690e4d14 +size 9520 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f1fd70f83d68bef435e9020d2536fe5cf9b71b5 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e96981215f9a8cf340d953552eadb983fa7e25b61757c6b66e165120fc8452b4 +size 32399 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/991578a811badaafd2a307b7680defb4_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/991578a811badaafd2a307b7680defb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a034a8df0e4f4817d5535dfdf4a4d577b6ed6d7 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/991578a811badaafd2a307b7680defb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a41b45d5ce788efe626e054dfe26e117027f8a0d2f7bcd1be35339171b0c22b7 +size 9883 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/9bc0626d1e98decce2afc2e7111ed670_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/9bc0626d1e98decce2afc2e7111ed670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a7fc48b4364e00d0920c6659f970190b41fd3cd --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/9bc0626d1e98decce2afc2e7111ed670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ecd12d35a1cbfdd60360482a5ec50569ca4fb2e3d47bee7ffc749215c036e3d +size 13256 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..135117a73c76e0c1490e2e9a2fa9d3a98562b25b --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b09dbf968d6ad8c7d94967d58b3b426a023dcfc4afafee45d096b97cd724304 +size 85897 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5671c02c254387b3aa1a782ce98444f2f27e31ce --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45333b042c727bdbdcf2dd004088c73031ba33b6135440a5b44ead3bbad77e74 +size 93983 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d108b103a6c39ec7c79b313be75f0892759b1669 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4d66f4f76f6ec4809378f75310e18c403fbd4a29a8f8ae9ecdec2cf9385b36f +size 15388 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73eed620d74ed5b3fb08325e243060d0bc2e0531 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:638e67fdb14845991bbe7cf5697c2522c83f4de526b31c93660b78e550415244 +size 127020 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9d2c2b4ab08b81e5fe1d313a43f2ae12c5b9faf --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:539dbb464c35a4238fb4457020d71d9aff05be163f1ba0a27247354ca001d8bf +size 31541 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/af06598cfb31b517e79b50d74f72a0ca_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/af06598cfb31b517e79b50d74f72a0ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1d7aed707ad03e9c702ee9dfc2c4cb10074c4a1 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/af06598cfb31b517e79b50d74f72a0ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94eef6813402fe83f1e0ec4e0f97f2b484edded0d0e235a6b9c9404383892fab +size 161010 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f8e53b857325620802ed963668034643140977a --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58d707ab6ceee4de0cf51309c78431c331c0aaef9e286f14613e728c768d9d58 +size 127430 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/bfbd7b26cfc0e087d62300ccdda068b4_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/bfbd7b26cfc0e087d62300ccdda068b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90fdf5208ed0a49d94d3c56f31222d28fed4e773 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/bfbd7b26cfc0e087d62300ccdda068b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:272174faf3fc52da8460abccc56b1f7b1ad8c547aa45999717d38ef09f699f6e +size 11005 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f13ff713d19d3e4c718ab32c3aefe5f4b77daec --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6afc8068111bcb332893e1da4446ca60dc3236dc1864952e84a6e795f99a0774 +size 31641 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e28f18b6478a38fbf684910cb7c6a1f42a53ed21 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d32531e58e7a72b5b56a7e0a70f2a259a7ea6ebafbf83a371c915ee97b08fa3 +size 35303 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17645f9442c7b15c809f760f3f6bd83e46d81d7b --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93742e80bfd90302769605eab5b2ec18fe2df64c8096b39c69d574ef46b8cbdd +size 26311 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f9b2e25a709b9a347ca05d8fe760bc21cbd2ac0 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e53899973536b4fcdd9e954823413f6b5b68ddc8109bccfa8d42c33f7764f05d +size 83475 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d741c43b8a5bd7eb178bc323a52de473d972d5da --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c440a564138fbcd4d40c035bde0083f18490e157a9ba46951d346dd64a5c06c9 +size 104305 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41c345922985a4a2c82cfb7b9d85976402de5a6d --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62bfac7d1a614a427a6ef9d74d3b63a2442227324f4efdeaf42b38d99ab2c7a9 +size 80072 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/dfed00213eb9b7aaadaf3d37576dabcf_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/dfed00213eb9b7aaadaf3d37576dabcf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b88621e8d5eeb672c6e5a3bb286dd5307b6f8a2 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/dfed00213eb9b7aaadaf3d37576dabcf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65c41d4cac4e169f16ec6a6a4c9b163e581b229d87059c583324d1631f1b3d56 +size 11466 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/e633d058b83b28c494f181a909dbfa09_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/e633d058b83b28c494f181a909dbfa09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81eebde82d2c7e5cc8eb2ea47029f73e4e6a0682 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/e633d058b83b28c494f181a909dbfa09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c06923eac325392bfda97ac5cb914f54bc940b3428dcdec08d4602f4466d80fe +size 10746 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec6683ea82c21b49b2e7c1521be3ca7226fa4883 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8d951b408b8e66be9e42ca2533e91df22c2166ad343c0b016121bbd479d1032 +size 92919 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/f20f1aa269b6d2bd7bf5ab4ce458a449_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/f20f1aa269b6d2bd7bf5ab4ce458a449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79c7be54ce43943fd001180f1a6e6cda5d13bb4f --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/f20f1aa269b6d2bd7bf5ab4ce458a449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2480982011be6e0dbd6816b4dc9ed2b452250e219170a5272e5d25eee6f7406e +size 13514 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/f3a15779c4bf10c99102c4d42bf67f1a_img.jpg b/marked/G/T-REC-G.8152-202401-I_PDF-E/f3a15779c4bf10c99102c4d42bf67f1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb30c29a8db3d56088d2ac861146b628d5367cf5 --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/f3a15779c4bf10c99102c4d42bf67f1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:446ad7033b88d2e8e7254a6b5e92ad47f9aa676e820917967657b07e0e3a386b +size 9449 diff --git a/marked/G/T-REC-G.8152-202401-I_PDF-E/raw.md b/marked/G/T-REC-G.8152-202401-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..24696777b0984d30a8dbbf6e08312561a3e6b8aa --- /dev/null +++ b/marked/G/T-REC-G.8152-202401-I_PDF-E/raw.md @@ -0,0 +1,1761 @@ + + +# Recommendation**ITU-T G.8152 (01/2024)** + +SERIES G: Transmission systems and media, digital systems and networks + +Packet over Transport aspects – MPLS over Transport aspects + +--- + +### **Protocol-neutral management information model for MPLS-TP network elements** + + + +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 superimposed 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 | +| 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 | +| Ethernet over Transport aspects | G.8000-G.8099 | +| MPLS over Transport aspects | G.8100-G.8199 | +| Synchronization, quality and availability targets | G.8200-G.8299 | +| Mobile network transport aspects | G.8300-G.8399 | +| Service Management | G.8600-G.8699 | +| ACCESS NETWORKS | G.9000-G.9999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T G.8152 + +# Protocol-neutral management information model for MPLS-TP network elements + +## Summary + +Recommendation ITU-T G.8152 contains the protocol neutral unified modelling language (UML) model for multi-protocol label switching-transport profile (MPLS-TP) network element (NE) management. + +This Recommendation provides a representation of the MPLS-TP technology using the methodologies that have been used for other transport technologies (e.g., synchronous digital hierarchy, optical transport network and Ethernet). + +The 2018 revision of this Recommendation up-versions the UML model tool to Papyrus v3.2.0 and the profile to v0.2.13, updates the model to add the maintenance entity group end point (MEP) proactive measurement management information (MI), MEP configuration MI and maintenance entity group intermediate point (MIP) configuration MI, adds the Spec model for MPLS-TP model, replaces the G.8152NetworkElement and MT\_NE with MT\_ConstraintDomain, and MT\_SubnetworkProtectionGroup specifies the FcSwitch, and MT\_CrossConnection specifies the ForwardingConstruct. + +Edition 3.0 of this Recommendation updates the MPLS-TP model to prune and refactor the TTP, CTP, Connectivity, Auxiliary MEP and MIP object classes from the G.7711 core model object classes, and up-versions the modelling tool to Eclipse 2020-06 (4.16) and Papyrus 4.8. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|---------------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.8152/Y.1375 | 2016-12-22 | 15 | 11.1002/1000/13104 | +| 2.0 | ITU-T G.8152/Y.1375 | 2018-12-14 | 15 | 11.1002/1000/13799 | +| 3.0 | ITU-T G.8152 | 2024-01-13 | 15 | 11.1002/1000/15829 | + +## Keywords + +Information model, MPLS-TP, protocol-neutral, transport resource, UML. + +--- + +\* To access the Recommendation, type the URL
MT/MT_A_So_MI | ITU-T G.8121
MT/MT_A_Sk_MI | ITU-T G.8152 v4.0
object class | +|-------------------|-------------------------------|-------------------------------|------------------------------------| +| TTP associated M | Admin_State | Admin_State | MtTtp | +| | Mode | Mode | MtMuxServerTtpPac | +| | APS_CoS | | MtMuxServerTtpSourcePac | +| | APS_OAM_Tool | APS_OAM_Tool | MtMuxServerTtpPac | +| CTP associated MI | Label[1...M] | Label[1...M] | MtMuxClientCtpPac | +| | LSPTYPE[1...M] | LSPTYPE[1...M] | MtMuxClientCtpPac | +| | CoS[1...M] | CoS[1...M] | MtMuxClientCtpPac | +| | PHB2TCMapping[1...M] | TC2PHBMapping[1...M] | MtMuxClientCtp
[Source Sink]Pac | +| | QoSEncodingMode[1...M] | QoSDecodingMode[1...M] | MtMuxClientCtp
[Source Sink]Pac | +| | LCK_Period[1...M] | LCK_Period[1...M] | MtMuxClientCtpPac | +| | LCK_CoS[1...M] | LCK_CoS[1...M] | MtMuxClientCtpPac | +| | LCK_OAM_Tool[1...M] | LCK_OAM_Tool[1...M] | MtMuxClientCtpPac | +| | GAL_Enable[1...M] | GAL_Enable[1...M] | MtMuxClientCtpPac | +| | | AIS_Period[1...M] | MtMuxClientCtpSinkPac | +| | | AIS_CoS[1...M] | MtMuxClientCtpSinkPac | +| | | AIS_OAM_Tool[1...M] | MtMuxClientCtpSinkPac | + + + +The diagram illustrates the MPLS-TP multiplexing model overview, showing the hierarchy and associations of various object classes. + +- MtMuxClientCtpPac (itut-mpls-tp::ObjectClasses (New))** + - Attributes: `cos: Integer [1]`, `galEnable: Boolean [1]`, `label: Integer [1]`, `lckCos: Integer [1] = 7`, `lckOamTool: OamTool [1]`, `lckPeriod: LckAisPeriod [1] = 1S`, `lspType: LspType [1]`. +- MtMuxClientCtpSourcePac (itut-mpls-tp::ObjectClasses (New))** + - Attributes: `phb2TcMapping:
LMDM (G.8121.2) | +| | | one-way synthetic | – | +| | | two-way synthetic | SLM (G.8121)
LM (G.8121.2)
LMDM (G.8121.2) | +| | Delay measurement (DM) | one-way (1) | IDM (G.8121) | +| | | two-way | DM (G.8121, G.8121.2)
LMDM (G.8121.2) | +| On-demand measurement | Loss measurement | two-way | LM (G.8121, G.8121.2),
LMDM (G.8121.2) | +| | | one-way synthetic | – | +| | | two-way synthetic | SLM (G.8121)
LM (G.8121.2)
LMDM (G.8121.2) | +| | Delay measurement | one-way | IDM (G.8121, G.8121.1) | +| | | two-way | DM (G.8121, G.8121.1,
G.8121.2)
LMDM (G.8121.2) | + +**Table A.1 – OAM capability support** + +| OAM function | | | OAM mechanism | +|----------------------------|-------------------------------------------------------------------|---------------------------|--------------------------------------------| +| | Maintenance | one-way throughput test | 1TH (G.8121, G.8121.1) | +| | | On-demand loop back | CV (G.8121, G.8121.1, G.8121.2) | +| | | On-demand link trace (LT) | CV (G.8121)
CV (G.8121.2) | +| Proactive fault management | Continuity check and connectivity verification | | CC/CV (G.8121, G.8121.2)
CCM (G.8121.1) | +| | Remote defect indication | | RDI (G.8121, G.8121.1, G.8121.2) | +| | Alarm indication signal | | AIS (G.8121, G.8121.1, G.8121.2) | +| | Locked signal (Lock report) | | LCK (G.8121, G.8121.1, G.8121.2) | +| On-demand fault management | Connectivity verification | | CV (G.8121, G.8121.1, G.8121.2) | +| | Lock instruction | | LKI (G.8121.2) | +| | Automatic protection switching | | APS (G.8121) | +| | Management communication channel/Signalling communication channel | | MCC/SCC (G.8121) | + +NOTE 1 – OAM mechanisms for MEP are all the OAMs specified in the [ITU-T G.8121] series. (The exception is APS, which NCM MEP does not support.) + +NOTE 2 – OAM mechanism for MIP is (on-demand) CV only. + +### A.1.1 MEP compound function + +There are two different types of MEP compound function: + +- mandatory NCM MEPs at the boundary of a layer network, monitoring an NC; +- optional TCM MEPs in the middle of a layer network, monitoring a tandem connection. + +See Figure A.1. + + + +Diagram illustrating Mandatory and optional MEPs. It shows a sequence of network elements: a green triangle (MEP), a yellow triangle (MIP), a yellow triangle (MIP), a pink triangle (MIP), a pink triangle (MIP), and a green triangle (MEP). The first green triangle is labeled 'Optional tandem connection maintenance entity'. The second green triangle is labeled 'Optional tandem connection maintenance entity'. A long double-headed arrow at the bottom is labeled 'Mandatory network connection maintenance entity'. The diagram is labeled G.8152(24). + +**Figure A.1 – Mandatory and optional MEPs** + +From the management perspective, an MEP has the following constraints. + +- An MEP can be unidirectional or bidirectional; unidirectional MEPs have a limited set of OAM functionality. +- An MEP belongs to one, and only one, MEL. MEPs terminate MEGs and each MEG is associated to one MEL. +- An MEP is addressed by one, and only one, medium access control (MAC) address. The MAC address (or more precisely the EUI-48) is bound to a physical subsystem and one + +physical subsystem can hold thousands of MEP functions, and all those MEP functions share in such case one MAC address. + +The MEP compound function supports three applications that are organized in types of job: + +- on-demand measurement; +- proactive measurement; +- maintenance. + +See Figure A.2. + + + +``` + +classDiagram + class Mep { + adminState: AdminState [1] = NORMAL + cvOamTool: OamTool [1] = N/A + dpLoopbackEnable: Boolean [1] + megId: String [1] + ccOamTool: OamTool [1] = N/A + rdiOamTool: OamTool [1] = N/A + ccEnable: Boolean [1] = false + cvpEnable: Boolean [1] = false + ccCos: Integer [1] = 7 + ccPeriod: OamPeriod [1] = 100MS + 1ThOamTool: OamTool [1] + mepId: String [1] + } + class MepSource { + ttlValue: Integer [1] = 255 + lockInstructEnable: Boolean [1] + adminState: AdminState [1] = NORMAL + } + class MepSink { + peerMepIdentifier: String [1] + aisOamTool: OamTool [1] + lckOamTool: OamTool [1] + } + class MepSourceDot1 + class MepSinkDot1 + class MepSourceDot2 { + fecChecking: Boolean [1] + targetFEC: String [1] + } + class MepSinkDot2 + class MepBidirectional + class OamPeriod { + <
MTDe_TT_So_MI | ITU-T G.8121
MTDe_TT_Sk_MI | ITU-T G.8121.1
MTDe_TT_So_MI | ITU-T G.8121.1
MTDe_TT_Sk_MI | ITU-T G.8121.2
MTDe_TT_So_MI | ITU-T G.8121.2
MTDe_TT_Sk_MI | +|-------------------------------------------------------|-----------------------------------------------|-------------------------------|------------------------------------------|---------------------------------|--------------------------------------------------------------|---------------------------------| +| General | GAL_Enable | GAL_Enable | GAL_Enable | GAL_Enable | GAL_Enable | GAL_Enable | +| | TTLVALUE | | TTLVALUE | | | | +| | | | MEP_ID | MEP_ID | | | +| Two-way on-demand loss of frame measurement | LMo_OAM_Tool | LMo_OAM_Tool | LMo_OAM_Tool | LMo_OAM_Tool | LMo_OAM_Tool | LMo_OAM_Tool | +| | LMo_Start(CoS,Period)[1..MLMo] | | LMo_Start(CoS,Period)[1..MLMo] | | LMo_Start(CoS, Test ID, Period, LMType, CountBytes)[1..MLMo] | | +| | LMo_Intermediate_Request[1..MLMo] | | LMo_Intermediate_Request[1..MLMo] | | LMo_Intermediate_Request[1..MLMo] | | +| | LMo_Terminate[1..MLMo] | | LMo_Terminate[1..MLMo] | | LMo_Terminate[1..MLMo] | | +| | LMo_Result(N_TF,N_LF,F_TF,F_LF)[1..MLMo] | | LMo_Result(N_TF,N_LF,F_TF,F_LF)[1..MLMo] | | LMo_Result(N_TF, N_LF, F_TF, F_LF)[1..MLMo] | | +| | | | | | LMo_ReportError(Error)[1..MLMo] | | +| | | | | | LMo_PeriodChanged[1..MLMo] | | +| One-way on-demand synthetic loss of frame measurement | | | | | | | +| | | | | | | | +| | | | | | | | +| Two-way on-demand synthetic loss of frame measurement | SLo_OAM_Tool | SLo_OAM_Tool | | | | | +| | SLo_Start(CoS,Test_ID,Length,Period)[1..MSLo] | | | | | | +| | SLo_Intermediate_Request[1..MSLo] | | | | | | +| | SLo_Terminate[1..MSLo] | | | | | | +| | SLo_Result(N_TF,N_LF,F_TF,F_LF)[1..MSLo] | | | | | | +| | IDMo_OAM_Tool | IDMo_OAM_Tool | IDMo_OAM_Tool | IDMo_OAM_Tool | | | + +**Table A.2 – On-demand measurement and maintenance MI list** + +| Functionality | ITU-T G.8121
MTDe_TT_So_MI | ITU-T G.8121
MTDe_TT_Sk_MI | ITU-T G.8121.1
MTDe_TT_So_MI | ITU-T G.8121.1
MTDe_TT_Sk_MI | ITU-T G.8121.2
MTDe_TT_So_MI | ITU-T G.8121.2
MTDe_TT_Sk_MI | +|--------------------------------------------------------|-------------------------------------------------------------------|---------------------------------------------------|------------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------|---------------------------------| +| One-way on-demand frame delay measurement | 1DMo_Start (CoS, Test_ID, Length, Period)[1...M 1DMo ] | 1DMo_Start(Test_ID)[1...M 1DMo ] | 1DMo_Start (CoS, Length, Period)[1...M 1DMo ] | 1DMo_Start[1...M 1DMo ] | | | +| | 1DMo_Terminate[1...M 1DMo ] | 1DMo_Terminate[1...M 1DMo ] | 1DMo_Terminate[1...M 1DMo ] | 1DMo_Terminate[1...M 1DMo ] | | | +| Two-way on-demand frame delay measurement | DMo_OAM_Tool | DMo_OAM_Tool | DMo_OAM_Tool | DMo_OAM_Tool | DMo_OAM_Tool | DMo_OAM_Tool | +| | DMo_Start (CoS, Test_ID, Length, Period)[1...M DMo ] | | DMo_Start (CoS, Length, Period)[1...M DMo ] | | DMo_Start(CoS, Test_ID, Length, Period, CopyPad)[1...M DMo ] | | +| | DMo_Intermediate_Request[1...M LMo ] | | DMo_Intermediate_Request[1...M LMo ] | | DMo_Intermediate_Request[1...M LMo ] | | +| | DMo_Terminate[1...M DMo ] | | DMo_Terminate[1...M DMo ] | | DMo_Terminate[1...M DMo ] | | +| | DMo_Result(count, B_FD[], F_FD[], N_FD[])[1...M DMo ] | 1DMo_Result(count, N_FD[])[1...M DMo ] | DMo_Result(count, B_FD[], F_FD[], N_FD[])[1...M DMo ] | | DMo_Result(count, B_FD[], F_FD[], N_FD[])[1...M DMo ] | | +| | | | | | DMo_ReportError(Error)[1...M DMo ] | | +| | | | | | DMo_PeriodChanged[1...M DMo ] | | +| Two-way on-demand frame loss / frame delay measurement | | | | | LMo_OAM_Tool (Note1) | | +| | | | | | DMo_OAM_Tool (Note2) | | +| | | | | | LMo_Start(CoS, Test_ID, Length, Period, LMType, CountBytes, CopyPad)[1...M LMo ] | | +| | | | | | LMo_IntermediateReport[1...M LMo ] | | +| | | | | | LMo_Terminate[1...M LMo ] | | +| | | | | | LMo_Result(N_TF, N_LF, F_TF, F_LF)[1...M LMo ] | | + +**Table A.2 – On-demand measurement and maintenance MI list** + +| Functionality | ITU-T G.8121
MTDe_TT_So_MI | ITU-T G.8121
MTDe_TT_Sk_MI | ITU-T G.8121.1
MTDe_TT_So_MI | ITU-T G.8121.1
MTDe_TT_Sk_MI | ITU-T G.8121.2
MTDe_TT_So_MI | ITU-T G.8121.2
MTDe_TT_Sk_MI | +|-------------------------|-------------------------------|-------------------------------|-------------------------------------|---------------------------------|------------------------------------------------------------------------------------------------|---------------------------------| +| | | | | | DMo_Result(count, B_FD[], F_FD[], N_FD[])[1...MDMo] | | +| | | | | | LMo_ReportError(Error)[1...MLMo] | | +| | | | | | LMo_PeriodChanged[1...MLMo] | | +| On-demand loop back | CV_OAM_Tool | CV_OAM_Tool | CV_OAM_Tool | CV_OAM_Tool | CV_OAM_Tool | CV_OAM_Tool | +| | CV_Series() | | CV_Series (TTL,CoS,N,Length,Period) | | CV_Series (Session_ID, Count, Period, CoS, Size, ValidateFEC, ValidateReverse, TargetFECStack) | | +| | CV_Series_Result() | | CV_Series_Result(REC,ERR,OO) | | FEC_Checking | FEC_Checking | +| | | | | | Target_FEC | FEC_Checking | +| | | | | | CV_Series_Result(Session_ID, Rcv, OOO, FWErr, BWErr) | | +| | | | | | CV_FWErr(Session_ID, Seq, RC, SubRC, ErrTLV) | | +| | | | | | CV_BWErr(Session_ID, Seq, RC, SubRC, ErrTLV) | | +| On-demand lock instruct | Admin_State | Admin_State_Request | | | Admin_State | Admin_State_Request | +| | Lock_Instruct_Enable | | | | Lock_Instruct_Enable | | +| | LI_Period | | | | LI_Period | | +| | LI_MEPID | | | | LI_MEPID | | +| | LI_CoS | | | | LI_CoS | | + +**Table A.2 – On-demand measurement and maintenance MI list** + +| Functionality | ITU-T G.8121
MTDe_TT_So_MI | ITU-T G.8121
MTDe_TT_Sk_MI | ITU-T G.8121.1
MTDe_TT_So_MI | ITU-T G.8121.1
MTDe_TT_Sk_MI | ITU-T G.8121.2
MTDe_TT_So_MI | ITU-T G.8121.2
MTDe_TT_Sk_MI | +|-----------------------------------|---------------------------------|------------------------------------|------------------------------------------------|------------------------------------|--------------------------------------------------------------------------|---------------------------------| +| One-way on-demand throughput test | 1TH_OAM_Tool | 1TH_OAM_Tool | 1TH_OAM_Tool | 1TH_OAM_Tool | | | +| | 1TH_Start (CoS, Length, Period) | 1TH_Start | 1TH_Start (CoS, Pattern, Length, Period) | 1TH_Start (Period) | | | +| | 1TH_Terminate | 1TH_Terminate | 1TH_Terminate | 1TH_Terminate | | | +| | 1TH_Result(Sent) | 1TH_Result(REC,CRC,BE R,OO) | 1TH_Result(Sent) | 1TH_Result(REC,CRC,BE R,OO) | | | +| | | | | | | | +| On-demand LT | CV_OAM_Tool | CV_OAM_Tool | CV_OAM_Tool | CV_OAM_Tool | CV_OAM_Tool | CV_OAM_Tool | +| | | | | | CV_Trace (Session_ID, CoS, ValidateFEC, ValidateReverse, TargetFECStack) | | +| | | | | | CV_Trace_Result (Session_ID, Result) | | +| | | | | | CV_FWErr(Session_ID, Seq, RC, SubRC, ErrTLV) | | +| | | | | | CV_BWErr(Session_ID, Seq, RC, SubRC, ErrTLV) | | +| | | | | | | | +| On-demand test | CV_OAM_Tool | CV_OAM_Tool | CV_OAM_Tool | CV_OAM_Tool | | | +| | | | CV_Test (CoS, Pattern, Length, Period) | | | | +| | | | CV_Terminate | | | | +| | | | CV_Test_Result(Sent, REC, REC, ERR, OO) | | | | + +#### A.1.1.2 MEP proactive measurement function + +The MEP proactive measurement function exists in NCM and TCM MEPs. See Figure A.4. + + + +The diagram illustrates two types of MEP structures for proactive measurement. On the left, the 'NCM MEP' (Network Connection Management MEP) is shown within a pink rectangular box. It consists of a stack of components: an orange trapezoid labeled 'MT/MT' at the top, a red triangle labeled 'MT' below it, a white trapezoid labeled 'MTDe/MT' below that, and a white triangle labeled 'MTDe' at the bottom. Three lines enter the top 'MT/MT' component. On the right, the 'TCM MEP' (Transport Connection Management MEP) is shown within a blue rectangular box. It has a similar stack: a white trapezoid labeled 'MT/MT' at the top, a red triangle labeled 'MT' below it, a white trapezoid labeled 'MTDe/MT' below that, and a white triangle labeled 'MTDe' at the bottom. One line enters the top 'MT/MT' component. Below the diagrams is the text 'G.8152(24)'. + +Diagram of MEP proactive measurement function showing NCM MEP and TCM MEP structures. + +Figure A.4 – MEP proactive measurement function + +[ITU-T G.8121] specifies MI for proactive measurements as listed in Table A.3. + +Table A.3 – Pro-active measurement MI list + +| Functionality | ITU-T G.8121
MT_TT_So_MI | ITU-T G.8121
MT_TT_Sk_MI | ITU-T G.8121.1
MT_TT_So_MI | ITU-T G.8121.1
MT_TT_Sk_MI | ITU-T G.8121.2
MT_TT_So_MI | ITU-T G.8121.2
MT_TT_Sk_MI | +|---------------|-----------------------------|-----------------------------|-------------------------------|-------------------------------|-------------------------------|-------------------------------| +| General | GAL_Enable | GAL_Enable | GAL_Enable | GAL_Enable | GAL_Enable | GAL_Enable | +| | TTLVALUE | | TTLVALUE | | TTLVALUE | | +| | MEG_ID | MEG_ID | MEG_ID | MEG_ID | | | +| | MEP_ID | PeerMEP_ID | MEP_ID | PeerMEP_ID | MEP_ID | PeerMEP_ID | +| | | AIS_OAM_Tool | | | | | +| | | LCK_OAM_Tool | | | | | +| | | | | | | PM_ClearError | + +**Table A.3 – Pro-active measurement MI list** + +| Functionality | ITU-T G.8121
MT_TT_So_MI | ITU-T G.8121
MT_TT_Sk_MI | ITU-T G.8121.1
MT_TT_So_MI | ITU-T G.8121.1
MT_TT_Sk_MI | ITU-T G.8121.2
MT_TT_So_MI | ITU-T G.8121.2
MT_TT_Sk_MI | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------------------------|-------------------------------|-------------------------------|-------------------------------|-------------------------------| +| | | | | | | PM_Responder_Enable | +| Continuity check
and Connectivity
Verification | CC_OAM_Tool | CC_OAM_Tool | CC_OAM_Tool | CC_OAM_Tool | CC_OAM_Tool | CC_OAM_Tool | +| | RDI_OAM_Tool | RDI_OAM_Tool | RDI_OAM_Tool | RDI_OAM_Tool | RDI_OAM_Tool | RDI_OAM_Tool | +| | CC_Enable (Note1) | CC_Enable (Note1) | CC_Enable (Note2) | CC_Enable | CC_Enable[1...Mcccv] | | +| | CVp_Enable (Note1) | CVp_Enable (Note1) | | | CVp_Enable[1...Mcccv] | | +| | | | | | CCCV_Mode[1...Mcccv] | | +| | MEP_ID | PeerMEP_ID | MEP_ID | PeerMEP_ID | MEP_ID[1...Mcccv] | PeerMEP_ID[1...Mcccv] | +| | CC_CoS | CC_CoS | CC_CoS | CC_CoS | CC_CoS[1...Mcccv] | CC_CoS[1...Mcccv] | +| | CC_Period | CC_Period | CC_Period | CC_Period | CC_Period | CC_Period | +| | | Get_SvdCC | | Get_SvdCC | | Get_SvdCC[1...Mcccv] | +| | | SvdCC | | SvdCC | | SvdCC | +| NOTE 1 – MI_CC_Enable and MI_CVp_Enable are used to enable CC and CV functions respectively.
The possible combinations are:
– no CC function and no CV function: MI_CC_Enable = false and MI_CVp_Enable = false
– CC-only function: MI_CC_Enable = true and MI_CVp_Enable = false
– CC and CV functions: MI_CC_Enable = true and MI_CVp_Enable = true
NOTE 2 – MI_CVp_Enable defined in [ITU-T G.8121] is automatically configured true by setting MI_CC_Enable true. | | | | | | | +| One-way
proactive loss of
frame
measurement
using CC | CC_OAM_Tool | CC_OAM_Tool | CC_OAM_Tool | CC_OAM_Tool | | | +| | ILMp_Enable | ILMp_Enable | LMC_Enable | LMC_Enable | | | +| | | | MEP_ID | PeerMEP_ID | | | +| | | | CC_CoS | CC_CoS | | | +| | | | CC_Period | CC_Period | | | + +**Table A.3 – Pro-active measurement MI list** + +| Functionality | ITU-T G.8121
MT_TT_So_MI | ITU-T G.8121
MT_TT_Sk_MI | ITU-T G.8121.1
MT_TT_So_MI | ITU-T G.8121.1
MT_TT_Sk_MI | ITU-T G.8121.2
MT_TT_So_MI | ITU-T G.8121.2
MT_TT_Sk_MI | +|-------------------------------------------------------|-----------------------------|-----------------------------|-------------------------------|-------------------------------|-----------------------------------------------|----------------------------------| +| Two-way proactive loss of frame measurement | LMp_OAM_Tool | LMp_OAM_Tool | LMp_OAM_Tool | LMp_OAM_Tool | LMp_OAM_Tool | LMp_OAM_Tool | +| | LMp_Enable[1...MLMp] | LMp_Enable[1...MLMp] | LMp_Enable[1...MLMp] | LMp_Enable[1...MLMp] | LMp_Enable[1...MLMp] | LMp_Enable[1...MLMp] | +| | LMp_Period[1...MLMp] | | LMp_Period[1...MLMp] | | LMp_Period[1...MLMp] | | +| | LMp_CoS[1...MLMp] | LMp_CoS[1...MLMp] | LMp_CoS[1...MLMp] | LMp_CoS[1...MLMp] | LMp_CoS[1...MLMp] | | +| | | | | | LMp_Test_ID[1...MLMp] | | +| | | | | | LMp_LMType[1...MLMp] | | +| | | | | | LMp_CountBytes[1...MLMp] | | +| | | | | | LMp_PeriodChanged[1...MLMp] | | +| | | | | | | LMp_ReportError(Error)[1...MLMp] | +| | | LM_DEGM | | LM_DEGM | | | +| | | LM_M | | LM_M | | | +| | | LM_DEGTHR | | LM_DEGTHR | | | +| | | LM_TFMIN | | LM_TFMIN | | | +| One-way proactive synthetic loss of frame measurement | ISLp_OAM_Tool | ISLp_OAM_Tool | | | | | +| | ISLp_Enable[1...M1SLp] | ISLp_Enable[1...M1SLp] | | | | | +| | ISLp_Period[1...M1SLp] | | | | | | +| | ISLp_Test_ID[1...M1SLp] | ISLp_Test_ID[1...M1SLp] | | | | | +| | ISLp_Length[1...M1SLp] | | | | | | +| | ISLp_CoS[1...M1SLp] | | | | | | +| Two-way proactive synthetic loss of frame measurement | SLp_OAM_Tool | SLp_OAM_Tool | | | (covered by delay management proactive (DMp)) | (covered by DMp) | +| | SLp_Enable[1...MSLp] | SLp_Enable[1...MSLp] | | | | | +| | SLp_Period[1...MSLp] | | | | | | +| | SLp_Test_ID[1...MSLp] | | | | | | +| | SLp_Length[1...MSLp] | | | | | | + +**Table A.3 – Pro-active measurement MI list** + +| Functionality | ITU-T G.8121
MT_TT_So_MI | ITU-T G.8121
MT_TT_Sk_MI | ITU-T G.8121.1
MT_TT_So_MI | ITU-T G.8121.1
MT_TT_Sk_MI | ITU-T G.8121.2
MT_TT_So_MI | ITU-T G.8121.2
MT_TT_Sk_MI | +|-------------------------------------------|--------------------------------------|----------------------------------------------------------------------|------------------------------------|----------------------------------------------------------------------|------------------------------------------|--------------------------------------------------------------------| +| | SLp_CoS[1...M SLp ] | SLp_CoS[1... M SLp ] | | | | | +| One-way proactive frame delay measurement | 1DMp_OAM_Tool | 1DMp_OAM_Tool | | | | | +| | 1DMp_Enable[1...M 1DMp ] | 1DMp_Enable[1...M 1DMp ] | | | | | +| | 1DMp_Period[1...M 1DMp ] | | | | | | +| | 1DMp_Test_ID[1...M 1DMp ] | 1DMp_Test_ID[1...M 1DMp ] | | | | | +| | 1DMp_Length[1...M 1DMp ] | | | | | | +| | 1DMp_CoS[1...M 1DMp ] | | | | | | +| two-way proactive frame delay measurement | DMp_OAM_Tool | DMp_OAM_Tool | DMp_OAM_Tool | DMp_OAM_Tool | DMp_OAM_Tool | DMp_OAM_Tool | +| | DMp_Enable[1...M DMp ] | DMp_Enable[1... M DMp ] | DMp_Enable[1...M DMp ] | DMp_Enable[1... M DMp ] | DMp_Enable[1...M DMp ] | DMp_Enable[1... M DMp ] | +| | DMp_Period[1...M DMp ] | | DMp_Period[1...M DMp ] | | DMp_Period[1...M DMp ] | | +| | DMp_Test_ID[1...M DMp ] | | DMp_Test_ID[1...M DMp ] | | DMp_Test_ID[1...M DMp ] | | +| | DMp_CoS[1...M DMp ] | DMp_CoS[1... M DMp ] | DMp_CoS[1...M DMp ] | DMp_CoS[1... M DMp ] | DMp_CoS[1...M DMp ] | | +| | DMp_Length[1...M DMp ] | | DMp_Length[1...M DMp ] | | DMp_Length[1...M DMp ] | | +| | | | | | DMp_CopyPad[1...M DMp ] | | +| | | | | | DMp_PeriodChanged[1...M LMp ] | DMp_ReportError(Error)[1...M DMp ] | +| Fault cause list | | cSSF
cLCK
cLOC
cMMG
cUNM
cUNP
cUNC
cDEG
cRDI | | cSSF
cLCK
cLOC
cMMG
cUNM
cUNP
cUNC
cDEG
cRDI | | cSSF
cLCK
cLOC[]
cMMG
cUNM
cUNC
cDEG
cRDI | + +**Table A.3 – Pro-active measurement MI list** + +| Functionality | ITU-T G.8121
MT_TT_So_MI | ITU-T G.8121
MT_TT_Sk_MI | ITU-T G.8121.1
MT_TT_So_MI | ITU-T G.8121.1
MT_TT_Sk_MI | ITU-T G.8121.2
MT_TT_So_MI | ITU-T G.8121.2
MT_TT_Sk_MI | +|----------------------------|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|----------------------------------------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Performance primitive list | | pN_LF[1...P]
pN_TF[1...P]
pF_LF[1...P]
pF_TF[1...P]
pF_DS
pN_DS
pB_FD[1...P]
pB_FDV[1...P]
pN_FD[1...P]
pN_FDV[1...P]
pF_FD[1...P]
pF_FDV[1...P] | | pN_LF
pN_TF
pF_LF
pF_TF
pF_DS
pN_DS | | pN_LF[1...P]
pN_TF[1...P]
pF_LF[1...P]
pF_TF[1...P]
pF_DS
pN_DS
pB_FD[1...P]
pB_FDV[1...P]
pN_FD[1...P]
pN_FDV[1...P]
pF_FD[1...P]
pF_FDV[1...P] | + +#### **A.1.1.3 MEP configuration function** + +The MEP configuration function exists in NCM and TCM MEPs. See Figure A.5. + + + +The diagram illustrates two Network Element Management (MEP) configurations. On the left, the 'NCM MEP' is shown within a pink rectangular box. It consists of a red trapezoidal block labeled 'MT/MT' at the top, connected to a white triangular block labeled 'MT', which is connected to a white trapezoidal block labeled 'MTDe/MT', which is finally connected to a white triangular block labeled 'MTDe'. The label 'NCM MEP' points to the top 'MT/MT' block. On the right, the 'TCM MEP' is shown within a blue rectangular box. It has an identical stack of blocks: 'MT/MT' (red trapezoid), 'MT' (white triangle), 'MTDe/MT' (white trapezoid), and 'MTDe' (white triangle). The label 'TCM MEP' points to its top 'MT/MT' block. Both configurations show a vertical stack of these four blocks. + +Diagram showing NCM MEP and TCM MEP configurations. Both show a stack of MT, MTDe/MT, and MTDe blocks. The NCM MEP is in a pink box, and the TCM MEP is in a blue box. Labels 'NCM MEP' and 'TCM MEP' point to the top MT/MT blocks. + +G.8152(24) + +**Figure A.5 – MEP configuration function** + +[ITU-T G.8121] specifies MI to configure an MEP as listed in Table A.4. + +**Table 0A.4 – MEP configuration MI list** + +| Functionality | ITU-T G.8121
MT/MT_A_So_MI | ITU-T G.8121
MT/MT_A_Sk_MI | ITU-T G.8121.1
MT/MT_A_So_MI | ITU-T G.8121.1
MT/MT_A_Sk_MI | ITU-T G.8121.2
MT/MT_A_So_MI | ITU-T G.8121.2
MT/MT_A_Sk_MI | +|--------------------------------|-------------------------------|-------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------| +| General | GAL_Enable | GAL_Enable | | | | | +| | TTLVALUE | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| Lock | Admin_State | Admin_State | | | | | +| | LCK_Period | LCK_Period | | | | | +| | LCK_CoS | LCK_CoS | | | | | +| | LCK_OAM_Tool | LCK_OAM_Tool | | | | | +| Alarm indication signal (Note) | AIS_Period | AIS_Period | | | Local_Defect | | +| | AIS_CoS | AIS_CoS | | | | | +| | AIS_OAM_Tool | AIS_OAM_Tool | | | | | +| Client signal fail | CSF_Tool | CSF_Tool | | | | | +| | CSF_Period | | | | | | +| | CSF_CoS | | | | | | +| | CSF_Enable | | | | | | +| | CSFrdifdiEnable | CSFrdifdiEnable | | | | | +| | | CSF_Reported | | | | | +| Automatic protection switching | APS_OAM_Tool | APS_OAM_Tool | | | | | +| | APS_CoS | | | | | | + +NOTE – MI for AIS at source is configured at server MEP. + +### A.1.2 MIP compound function + +See Figures A.6 and A.7. + + + +Diagram of a full MIP (Management Information Plane) configuration. A central yellow diamond-shaped node has four ports labeled a, b, c, and d. Port 'a' is connected to an external source 'A' and has a callout box for Table 9-9/ITU-T G.8121 (MI GAL\_Enable, MI\_MIP\_ID, MI\_CV\_OAM\_Tool, MI\_DP\_Loopback\_Enable). Port 'b' is connected to an external destination 'Z' and has a callout box for Table 9-8/ITU-T G.8121 (MI GAL\_Enable, MI\_TTLVALUE, MI\_MIP\_ID, MI\_CV\_OAM\_Tool, MI\_DP\_Loopback\_Enable). Port 'c' is connected to an external destination 'Z' and has a callout box for Table 9-9/ITU-T G.8121. Port 'd' is connected to an external source 'A' and has a callout box for Table 9-8/ITU-T G.8121. All four ports have a common callout box for Table 9-11/ITU-T G.8121 (MI\_DS\_MP\_Type). + +G.8152(24) + +Figure A.6 – MIP configuration parameters + + + +Diagram of 'half MIP' compound functions. The top part shows a 'down-half MIP' as a yellow triangle with two ports, 'a' and 'd'. Port 'a' is connected to an external destination 'Z' and port 'd' to an external source 'A'. Both ports have an 'AP' (Application Point) and a callout box for Table 9-11/ITU-T G.8121 (MI\_DS\_MP\_Type). The bottom part shows an 'up-half MIP' as a yellow triangle with two ports, 'b' and 'c'. Port 'b' is connected to an external destination 'Z' and port 'c' to an external source 'A'. Both ports have an 'AP' and a callout box for Table 9-11/ITU-T G.8121 (MI\_DS\_MP\_Type). + +G.8152(24) + +Figure A.7 – "half MIP" compound function + +The MI of the MIP compound function (specified in [ITU-T G.8121]) is mapped to the MipBidirectional object class. See Figure A.8. + + + +G.8152(24) + +Diagram showing Full MIP and Half MIP configuration functions. Full MIP consists of four stacked components: MTDi (red triangle), MTDi/MT (white diamond), MTDi/MT (red triangle), and MTDi (red triangle). Half MIP consists of two stacked components: MTDi/MT (red triangle) and MTDi (red triangle). + +**Figure A.8 – MIP/half MIP configuration function** + +[ITU-T G.8121] specifies MI to configure an MIP as listed in Table A.5. + +**Table 0A.5 – MIP configuration MI list** + +| Functionality | ITU-T G.8121
MTDi_TT_So_MI | ITU-T G.8121
MTDi_TT_Sk_MI | ITU-T G.8121.1
MTDi_TT_So_MI | ITU-T G.8121.1
MTDi_TT_Sk_MI | ITU-T G.8121.2
MTDi_TT_So_MI | ITU-T G.8121.2
MTDi_TT_Sk_MI | +|-----------------|-------------------------------------------------|-------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------| +| General | GAL_Enable | GAL_Enable | | | | | +| | TTLVALUE | | | | | | +| | MIP_ID | MIP_ID | | | | | +| | | DS_MP_Type [Note] | | | | | +| | [Note] DS_MP_type is configured at MTDi/MT_A_Sk | | | | | | +| On-demand
CV | CV_OAM_Tool | CV_OAM_Tool | | | Target_FEC | | +| | | | | | | | +| | | | | | | | +| | | | | | | | + +## **A.2 Fault management** + +For further study. + +## **A.3 Performance monitoring** + +Performance monitoring (PM) allows measurement of different performance parameters like frame loss ratio, frame delay and frame delay variation. + +### **A.3.1 Loss measurement** + +The frame LM provides performance data that is based on the lost frames between the ingress and the egress of an ME; i.e., between two MEPs. + +LM is restricted to MEGs which have only a single ME. + +The following LM functions are specified: + +- two-way on-demand LM; +- one-way on-demand synthetic LM; +- two-way on-demand synthetic LM; +- two-way proactive LM; +- one-way proactive synthetic LM; +- two-way proactive synthetic LM. + +The single-ended on-demand LM function is managed only at the source MEP. The sink MEP does not need any management. + +The dual-ended proactive LM function is managed at source and sink MEP. + +### **A.3.2 Delay measurement** + +The frame DM provides performance data that is based on the delay of the frames between the ingress and the egress of an ME; i.e., between two MEPs. + +The following DM functions are specified: + +- one-way on-demand DM; +- two-way (round-trip) on-demand DM; +- one-way proactive DM; +- two-way (round-trip) proactive DM. + +The one-way DM function is started at the source MEP and enabled at the sink MEP. + +The two-way DM function is managed only at the source MEP. The sink MEP does not need any management. + +## **A.4 MPLS-TP multiplexing** + +This clause maps the MPLS-TP multiplexing related MI to the corresponding object classes. + +The MPLS-TP multiplexing configuration function exists only in MT TTP and MT CTP. + +See Figure A.9. + + + +Diagram of MPLS-TP multiplexing configuration function showing two vertical stacks of components. The left stack is pink and labeled 'NCM MEP' at the top, containing 'MT/MT', 'MT', 'MTDe/MT', and 'MTDe'. The right stack is blue and labeled 'TCM MEP' at the top, containing 'MT/MT', 'MT', 'MTDe/MT', and 'MTDe'. Both stacks have input lines at the top and output lines at the bottom. A label 'G.8152(24)' is at the bottom right. + +**Figure A.9 – MPLS-TP multiplexing configuration function** + +[ITU-T G.8121] specifies MI to configure the MPLS-TP multiplexing function as listed in Table A.6. + +**Table A.6 – Mapping of multiplexing related MI to ITU-T G.8152 artefacts** + +| Functionality | ITU-T G.8121
MT/MT_A_So_MI | ITU-T G.8121
MT/MT_A_Sk_MI | +|-------------------|-------------------------------|-------------------------------| +| TTP associated MI | Label[1...M] | Label[1...M] | +| | LSPTType[1...M] | LSPTType[1...M] | +| | CoS[1...M] | CoS[1...M] | +| | PHB2TCMapping[1...M] | TC2PHBMapping[1...M] | +| | QoSEncodingMode[1...M] | QoSDecodingMode[1...M] | +| | Mode | Mode | +| CTP associated MI | | | + +## **A.5 Connection function** + +This clause maps the connection function related MI to the corresponding object classes. See Table A.7. + +**Table A.7 – Mapping of connection function related MI to ITU-T G.8152 artefacts** + +| Functionality | MT_C_MI | ITU-T G.8152 | +|----------------------------------------|-----------------------------------------------|--------------| +| General connection management | Create_MC | | +| | Modify_MC | | +| | Delete_MC | | +| Individual connection point management | MT_C_MP per input and output connection point | | +| | for further study | | +| Individual connection management | MT_C_MP per matrix connection: | | +| | MT_C_MI_ConnectionType | | +| | MT_C_MI_Return_CP_ID | | + +**Table A.7 – Mapping of connection function related MI to ITU-T G.8152 artefacts** + +| Functionality | MT_C_MI | ITU-T G.8152 | +|--------------------------------------------------------|-------------------------------------------------------------------|--------------| +| | MT_C_MI_ConnectionPortIds | | +| Sub-network connection protection (SNCP) configuration | MT_C_MP per SNC/S protection process:
for further study | | + +### A.5.1 Linear protection function + +The MPLS-TP linear protection function is specified in [ITU-T G.8131]. The related MI is listed in [ITU-T G.8121]. + +This function is modelled by the MT\_SNCP\_Group object class. + +See Figure A.10. + +![UML Class Diagram for MPLS-TP linear protection. The diagram shows the MT_SubNetworkConnectionProtectionGroup class and its associations with enumerations and an abstract class. MT_SubNetworkConnectionProtectionGroup has attributes: protectionType (ProtectionType [1] = 1_FOR_1_BIDIRECTIONAL_WITH_APC), holdOffTime (Integer [1] = 0), sncpGroupState (SncpGroupState [1]), and isSdProtectionEnabled (Boolean [1] = false). It uses ProtectionType, OperationType, SncpGroupState, and SwitchDirection enumerations. It also inherits from CoreModel::CoreNetworkModel::ObjectClasses::Resilience::FcSwitch via an abstraction, Specify, Cond relationship.](0f26e70157bd4c45f825795cdcd20fbd_img.jpg) + +``` + +classDiagram + class MT_SubNetworkConnectionProtectionGroup { + protectionType: ProtectionType [1] = 1_FOR_1_BIDIRECTIONAL_WITH_APC + holdOffTime: Integer [1] = 0 + sncpGroupState: SncpGroupState [1] + isSdProtectionEnabled: Boolean [1] = false + } + class ProtectionType { + <
| MI_MatrixControlper matrix connection:
MI_ConnectionType
MI_Return_CP_ID
MI_ConnectionPortIds
per SNCP protection group:
MI_PS_WorkingPortId
MI_PS_ProtectionPortId
MI_PS_ProtType
MI_PS_OperType
MI_PS_HoTime
MI_PS_WTR
MI_PS_ExtCMD
MI_PS_BridgeType
MI_PS_SD_Protection | | + +## II.2 MPLS-TP termination function (MT\_TT) + +See Table II.2. + +**Table II.2 – MI groupings of the MPLS-TP termination function** + +| Symbol | Management information | Managed object class | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| MPLS-TP (MT) trail termination source function | | | +|
| MI_GAL_EnableMI_TTLVALUE
MI_MEG_ID
MI_MEP_ID
MI_CC_OAM_Tool
MI_RDI_OAM_Tool
MI_CC_Enable
MI_CVp_Enable
MI_CC_CoS
MI_CC_Period
MI_LMp_OAM_Tool
MI_LMp_Enable[i]
MI_LMp_Period[i]
MI_LMp_CoS[i]
MI_DMp_OAM_Tool
MI_DMp_Enable[i]
MI_DMp_Period[i]
MI_DMp_Test_ID[i]
MI_DMp_CoS[i]
MI_DMp_Length[i]
MI_1DMp_OAM_Tool
MI_1DMp_Enable[i]
MI_1DMp_Period[i]
MI_1DMp_Test_ID[i]
MI_1DMp_Length[i]
MI_1DMp_CoS[i]
MI_SLP_OAM_Tool
MI_SLP_Enable[i]
MI_SLP_Period[i]
MI_SLP_Test_ID[i]
MI_SLP_Length[i]
MT_TT_So_MI_SLP_CoS[i] | | +| G.8121.1 specific | MI_LMC_Enable | | +| G.8121.2 specific | MI_CCCV_Mode[i]
MI_Local_Discr
MI_DMp_CopyPad[i]
MI_LMp_Test_ID[i]
MI_LMp_LMType[1...MLMp]
MI_LMp_CountBytes[i] | | +| MPLS-TP (MT) trail termination sink function | | | + +**Table II.2 – MI groupings of the MPLS-TP termination function** + +| Symbol | Management information | Managed object class | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +|
| MI_GAL_EnableMI_MEG_ID
MI_PeerMEP_ID
MI_CC_OAM_Tool
MI_RDI_OAM_Tool
MI_CC_Enable
MI_CVp_Enable
MI_CC_Period
MI_CC_CoS
MI_Get_SvdCC
MI_LMp_OAM_Tool
MI_LMp_Enable[i]
MI_LMp_CoS[i]
MI_LM_DEGM
MI_LM_M
MI_LM_DEGTHR
MI_LM_TFMIN
MI_DMp_OAM_Tool
MI_DMp_Enable[i]
MI_DMp_CoS[i]
MI_1DMp_OAM_Tool
MI_1DMp_Enable[i]
MI_1DMp_Test_ID[i]
MI_SLP_OAM_Tool
MI_SLP_Enable[i]
MI_SLP_CoS[i]
MI_AIS_OAM_Tool
MI_LCK_OAM_Tool
MI_1second | | +| G.8121.1 specific | MI_LMC_Enable | | +| G.8121.2 specific | MI_CCCV_Mode[i]
MI_Remote_Discr[i]
MI_PM_ClearError
MI_PM_Responder_Enable | | + +## II.3 MPLS-TP to MPLS-TP adaptation function (MT/MT\_A) + +See Table II.3. + +**Table II.3 – MI Groupings of the MPLS-TP to MPLS-TP adaptation function** + +| Symbol | Management information
(blue: client layer related
red: server layer related) | Managed object class | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| MPLS-TP to MPLS-TP adaptation source function | | | +|
| MI_ActiveMI_Admin_State
MI_Label[i]
MI_LSPTtype[i]
MI_CoS[i]
MI_PHB2TCMapping[i]
MI_QoSEncodingMode[i]
MI_Mode
MI_LCK_Period[i]
MI_LCK_CoS[i]
MI_LCK_OAM_Tool[i]
MI_GAL_Enable[i]
(NOTE – Should be MI_GAL_Enable set double (Server and client?))
MI_APS_CoS
MI_APS_OAM_Tool | | +| MPLS-TP to MPLS-TP adaptation sink function | | | +|
| MI_ActiveMI_AdminState
MI_Label[i]
MI_LSPTtype[i]
MI_CoS[i]
MI_TC2PHBMapping[i]
MI_QoSDecodingMode[i]
MI_Mode
MI_AIS_Period[i]
MI_AIS_CoS[i]
MI_AIS_OAM_Tool[i]
MI_LCK_Period[i]
MI_LCK_CoS[i]
MI_LCK_OAM_Tool[i]
MI_APS_OAM_Tool
MI_GAL_Enable [i]
(NOTE – Should be MI_GAL_Enable set double (Server and client?)) | | +| G.8121.2 specific | MI_Local_Defect[i] | | + +## II.4 MT diagnostic functions (MPLS-TP MEP diagnostic function (MTDe) and MPLS-TP diagnostic function within MTx MIP (MTDi)) + +See Table II.4. + +**Table II.4 – MI groupings of the MT diagnostic functions** + +| Symbol | Management information | Managed object class | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| MT diagnostic trail termination source function for MEP (MTDe_TT_So) | | | +|
| MI_GAL_EnableMI_TTLVALUE
MI_CV_OAM_Tool
MI_CV_Series ()
MTDe_TT_So_MI_1TH_OAM_Tool
MI_1TH_Start (CoS,Length,Period)
MI_1TH_Terminate
MI_LMo_OAM_Tool
MI_LMo_Start(CoS,Period) [i]
MI_LMo_Terminate[i]
MI_DMo_OAM_Tool
MI_DMo_Start (CoS,Test_ID,Length,Period)[i]
MI_DMo_Terminate[i]
MI_1DMo_OAM_Tool
MI_1DMo_Start(CoS,Test_ID,Length,Period)[i]
MI_1DMo_Terminate[i]
MI_SLo_OAM_Tool
MI_SLo_Start (CoS,Test_ID,Length,Period)[i]
MI_SLo_Terminate[i]
MI_Admin_State
MI_Lock_Instruct_Enable
MI_DP_Loopback_Enable | | +| G.8121.1 specific | MI_MEP_ID
MI_CV_Series (Target MEP/MIP ID, CoS, N, Length, Period)
MI_CV_Test(CoS, Pattern, Length, Period) | | + +**Table II.4 – MI groupings of the MT diagnostic functions** + +| Symbol | Management information | Managed object class | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| G.8121.2 specific | MI_CV_Series (Session_ID, Count, Period, CoS, Size, ValidateFEC, ValidateReverse, TargetFECStack)
MI_CV_Trace (Session_ID, CoS, ValidateFEC, ValidateReverse, TargetFECStack)
MI_FEC_Checking
MI_Target_FEC
MI_Ifnum
MI_MTU
MI_DMo_Start(CoS, Test_ID, Length, Period, CopyPad)[i]
MI_LMo_Start(CoS, Test_ID, Period, LMType, CountBytes)[i]
LMDMo_Start(CoS, Test_ID, Length, Period, LMType, CountBytes, CopyPad)[i]
MI_LMDMo_Terminate [i]
MI_LI_Period
MI_LI_MEPID
MI_LI_CoS | | +| MT diagnostic trail termination sink function for MEP (MTDe_TT_Sk) | | | +|
| MI_GAL_EnableMI_CV_OAM_Tool
MI_1TH_OAM_Tool
MI_1TH_Start
MI_1TH_Terminate
MI_LMo_OAM_Tool
MI_DMo_OAM_Tool
MI_1DMo_OAM_Tool
MI_1DMo_Start(Test_ID)[i]
MI_1DMo_Terminate[i]
MI_SLo_OAM_Tool
MI_DP_Loopback_Enable | | +| G.8121.1 specific | MI_MEP_ID
MI_1TH_Start(Period) | | +| G.8121.2 specific | MI_FEC_Checking
PM_Responder_Enable | | +| MT diagnostic trail termination source function for MIP (MTDi_TT_So) | | | + +**Table II.4 – MI groupings of the MT diagnostic functions** + +| Symbol | Management information | Managed object class | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|----------------------| +|
| MI_GAL_EnableMI_TTLVALUE
MI_MIP_ID
MI_CV_OAM_Tool
MI_DP_Loopback_Enable | | +| G.8121.2 specific | MI_Target_FEC
MI_Ifnum
MI_MTU | | +| MT diagnostic trail termination sink function for MIP (MTDi_TT_Sk) | | | +|
| MI_GAL_EnableMI_MIP_ID
MI_CV_OAM_Tool
MI_DP_Loopback_Enable | | +| G.8121.2 specific | MI_FEC_Checking | | + +## II.5 MPLS-TP to non-MPLS-TP client adaptation functions + +See Table II.5. + +**Table II.5 – MI groupings of the MPLS-TP to non-MPLS-TP client adaptation functions** + +| Symbol | Management information
(blue: client layer related
red: server layer related) | Managed object class | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| MPLS-TP to non-MPLS-TP client adaptation source functions | | | +|
| MI_AdminStateMI_FCSEnable
MI_CWEnable
MI_SQUse
MI_PRI2PSCMapping
MI_MEP_MAC*
MI_Client_MEL*
MI_LCK_Period*
MI_LCK_Pri*
MI_MEL*
*Ethernet (ETH) OAM related | | + +**Table II.5 – MI groupings of the MPLS-TP to non-MPLS-TP client adaptation functions** + +| Symbol | Management information
(blue: client layer related
red: server layer related) | Managed object class | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +|
| MI_Active
MI_ECC_CoS
MI_GAL_Enable
| | +|
| MI_Active
MI_ECC_CoS
MI_GAL_Enable
| | +| MPLS-TP to non-MPLS-TP client adaptation sink functions | | | +|
| MI_Admin_State
MI_LCK_Period *
MI_LCK_Pri *
MI_Client_MEL *
MI_MEP_MAC *
MI_AIS_Pri *
MI_AIS_Period *
MI_MEL
MI_FCSEnable
MI_CWEnable
MI_SQUse
MI_GAL_Enable
MI_CoS2PRIMapping
* ETH OAM related
| | +|
| MI_Active
MI_GAL_Enable
| | + +**Table II.5 – MI groupings of the MPLS-TP to non-MPLS-TP client adaptation functions** + +| Symbol | Management information(blue: client layer related
red: server layer related) | Managed object class | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|----------------------| +|
| MI_Active
MI_GAL_Enable
| | + +## II.6 Non-MPLS-TP server to MPLS-TP adaptation functions + +See Table II.6. + +**Table II.6 – MI groupings of the non-MPLS-TP server to MPLS-TP adaptation functions** + +| Symbol | Management information(blue: client layer related
red: server layer related) | Managed object class | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| Non-MPLS-TP server to MPLS-TP adaptation source functions | | | +|
Image: Diagrams of adaptation functions: Sn/MT_A_So, Sn-X-L/MT_A_So, Sm/MT_A_So, Sm-X-L/MT_A_So, ODUkp/MT_A_So, ODUkp-h/MT_A_So, Pq/MT_A_So, Pq/MT_A_Sk, and ETH/MT_A_So. Each diagram shows a trapezoidal block with input/output signals like SCC_CI, MT_CI, Sn_CI, Sn_AI, and MI interfaces.
|MI_Active
MI_SCCType (not in ETH/MT)
MI_Etype (only in ETH/MT)
MI_Label[1...M]
MI_LSPType[1...M]
MI_CoS[1...M]
MI_PHB2TCMapping[1...M]
MI_QoSEncodingMode[1...M]
MI_Mode[1...M]
MI_GAL_Enable[1...M]
Only in ODUkp-h/MT:
MI_INCREASE
MI_DECREASE
MI_TSNUM
MI_ODUflexRate
(blue: client layer related
red: server layer related) | Managed object class | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| Non-MPLS-TP server to MPLS-TP adaptation sink functions | | | +|
Image: Diagram showing a stack of adaptation sink function symbols. From top to bottom: Sn/MT_A_Sk, Sn-X-L/MT_A_Sk, Sm/MT_A_Sk, Sm-X-L/MT_A_Sk, ODUkP/MT_A_Sk, ODUkP-h/MT_A_Sk, Pq/MT_A_Sk, Pq-X-L/MT_A_Sk, and ETH/MT_A_Sk. Each symbol shows input signals like SCC_CI and MT_CI, and management interface MI. Reference G.8152(24) is at the bottom.
G.8152(24)
|MI_Active
MI_SCCType (not in ETH/MT)
MI_Etype (only in ETH/MT)
MI_Frame_Type_Config (only in ETH/MT)
MI_Label[1...M]
MI_LSPType[1...M]
MI_CoS[1...M]
MI_TC2PHBMapping[1...M]
MI_QoSDecodingMode[1...M]
MI_Mode
MI_LCK_Period[1...M]
MI_LCK_CoS[1...M]
MI_Admin_State
MI_AIS_Period[1...M]
MI_AIS_CoS[1...M]
MI_GAL_Enable[1...M]
MI_LCK_OAM_Tool [1...M]
MI_AIS_OAM_Tool[1...M]
Only in ODUkP-h/MT:
MI_INCREASE
MI_DECREASE
MI_AcSL
MI_AcEXI
MI_LastInvalidUPI
MI_cPLM
MI_cLFD
MI_cEXM
MI_cUPM (not ETH/MT)
| | +| G.8121.2 specific | MI_Local_Defect[i] | | + +Based on the groupings above the packages listed in Table II.7 have been identified. + +**Table II.7 – Derived MI groupings of the MPLS-TP functions** + +| MI groupings | Package/Object class name | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| TTP MI source grouping | | +| MI_Active | | +| MI_INCREASEMI_DECREASE
MI_TSNUM
MI_ODUflexRate | HaoCapableTtpSource_Pac | +| TTP MI sink grouping | | +| MI_Active | | +| MI_Frame_Type_Config | EthServerTtpSink_Pac | +| MI_INCREASE
MI_DECREASE | HaoCapableTtpSink_Pac | +| TTP MI grouping | | +| MI_SCCType | GfpMapping_Pac | +| MI_Etype | EthServerTtp_Pac | +| MT_CTP MI source grouping | | +| MI_PHB2TCMapping[1...M]
MI_QoSEncodingMode[1...M]
MI_APS_OAM_CoS[1...M] | MT_ConnectionTerminationPointSource | +| MT_CTP MI sink grouping | | +| MI_TC2PHBMapping[1...M]
MI_QoSDecodingMode[1...M]
MI_LCK_Period[1...M]
MI_LCK_CoS[1...M]
MI_Admin_State
MI_AIS_Period[1...M]
MI_AIS_CoS[1...M]
MI_LCK_OAM_Tool [1...M]
MI_AIS_OAM_Tool[1...M] | MT_ConnectionTerminationPointSink | +| MT_CTP MI grouping | | +| MI_Label[1...M]
MI_LSPTYPE[1...M]
MI_CoS[1...M]
MI_Mode[1...M]
MI_GAL_Enable[1...M]
MI_APS_OAM_Tool[1...M] | MT_ConnectionTerminationPoint | + +# **Appendix III** + +## **UML model data dictionary** + +(This appendix does not form an integral part of this Recommendation.) + +The DD contains, in MS Word document format, the details of the MPLS-TP NE management-protocol-neutral information model, including the description and properties of the object classes and their attributes and operations. These details information are generated automatically by a Gendoc tool from the UML model. + +The ITU-T G.8152 DD is provided in the G.8152\_v2.00\_DD.zip file at the repository website mentioned in clause 8. + +# Bibliography + +- [b-ITU-T Q.822] Recommendation ITU-T Q.822 (1994), *Stage 1, stage 2 and stage 3 description for the Q3 interface – Performance management.* +- [b-Eclipse-Papyrus] *Papyrus Eclipse UML Modelling Tool*
and SF-R detected at non-adjacent nodes..... | 104 | +| I.8 Unidirectional SF-R pre-empting a unidirectional SD-S on adjacent spans ..... | 105 | +| I.9 Unidirectional SF-R coexisting with a unidirectional SF-R on non-adjacent spans.. | 106 | +| I.10 Node failure on a ring with extra traffic capability (see Figure I.11)..... | 107 | +| I.11 Unidirectional SF-S pre-empting a unidirectional SF-R on adjacent spans –
SF-S and SF-R detected at adjacent nodes..... | 107 | +| Appendix II – Generalized squelching logic ..... | 127 | +| II.1 Squelching for unidirectional (and bidirectional) circuits..... | 127 | +| II.2 Squelching of multiply dropped and multiply sourced unidirectional circuits ..... | 127 | +| II.2.1 Multiply dropped unidirectional circuits..... | 127 | +| II.2.2 Multiply sourced unidirectional circuits ..... | 128 | +| II.2.3 Application to ring interworking..... | 128 | + + + +# **TYPES AND CHARACTERISTICS OF SDH NETWORK PROTECTION ARCHITECTURES** + +*(revised in 1998)* + +# **1 Scope** + +This Recommendation describes the various protection mechanisms for Synchronous Digital Hierarchy (SDH) networks, their objectives and their applications. + +Protection schemes are classified as: + +- SDH trail protection (at the section or path layer); +- SDH subnetwork connection protection (with inherent monitoring, non-intrusive monitoring, and sub-layer monitoring). + +Protection interworking (including switching hierarchy) and interconnection scenarios are under development in a separate Recommendation. + +OAM&P, performance, and satellite/radio aspects are for further study. Synchronization architecture and protection of synchronization are not described here. It is not necessary to have all protection mechanisms described within this Recommendation available on the same SDH equipment. + +# **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; 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)*. +- CCITT Recommendation G.774 (1992), *Synchronous Digital Hierarchy (SDH) management information model for the network element view*. +- ITU-T Recommendation G.783 (1997), *Characteristics of Synchronous Digital Hierarchy (SDH) equipment functional blocks*. +- ITU-T Recommendation G.784 (1994), *Synchronous Digital Hierarchy (SDH) management*. +- ITU-T Recommendation G.803 (1997), *Architectures of transport networks based on the Synchronous Digital Hierarchy (SDH)*. + +# 3 Terms and definitions + +This Recommendation defines the following terms: + +**3.1 APS controller:** That part of a node that is responsible for generating and terminating information carried in the APS protocol and implementing the APS algorithm. + +**3.2 Add/Drop Multiplex (ADM):** Network elements that provide access to all, or some subset of the constituent signals contained within an STM-N signal. The constituent signals are added to (inserted), and/or dropped from (extracted) the STM-N signal as it passes through the ADM. See 3.5/G.782. + +**3.3 add traffic:** Normal or extra traffic inserted into working, protection, or non-pre-emptible unprotected channels on the ring at a ring node. + +**3.4 Administrative Unit (AU):** See Recommendation G.707. + +**3.5 Alarm Indication Signal (AIS):** A code sent downstream in a digital network as an indication that an upstream failure has been detected and alarmed. It is associated with multiple transport layers. + +**3.6 APS request:** That set of signals into an APS controller that determines its behaviour. An APS request can be either an externally initiated command or an automatically initiated command. + +**3.7 AU-AIS:** See Recommendation G.783. + +**3.8 AU pointer:** See Recommendation G.707. + +**3.9 automatically initiated command:** An APS request that is initiated by any one of the following: 1) multiplex section performance criteria; 2) local equipment performance criteria; or 3) received bridge requests. + +**3.10 auto-provisioning:** The assignment of values to parameters within a network element, without those values being specifically entered externally by a user. + +**3.11 bidirectional connection:** See Recommendation G.803. An illustration is given in Figure 3-2. + +**3.12 bidirectional protection switching:** A protection switching architecture in which, for a unidirectional failure (i.e. a failure affecting only one direction of transmission), both directions (of the "trail", "subnetwork connection", etc.) including the affected direction and the unaffected direction, are switched to protection. + +**3.13 bidirectional ring:** In a bidirectional ring, normal routing of the normal traffic signals is such that both directions of a bidirectional connection travel along the ring through the same nodes, but in opposite directions. + +**3.14 Bit Interleaved Parity N (BIP-N):** See Recommendation G.707. + +**3.15 bridge:** The action of transmitting identical traffic on both the working and protection channels. + +**3.16 bridge request:** A message sent from a tail-end node to the head-end node requesting that the head-end perform a bridge of the normal traffic signals onto the protection channels. + +**3.17 bridge request status:** A message sent from a tail-end node to all other nodes within the protection system indicating that the tail-end has requested a bridge. + +**3.18 container:** See Recommendation G.707. + +**3.19 controller failure:** The condition during which a node is no longer able to correctly operate the APS protocol, but still generates a correctly formatted SDH frame. + +- 3.20 crossing K-bytes:** When a node sees ring bridge requests of equal priority on both 'sides' (This includes a switching node receiving a ring bridge request from the other end). +- 3.21 Data Communications Channel (DCC):** See Recommendation G.784. +- 3.22 dedicated protection:** A protection architecture that provides capacity dedicated to the protection of traffic-carrying capacity (1 + 1). See Recommendation G.803. +- 3.23 default APS code:** This term refers to the APS bytes transmitted with the source node ID equal to the destination node ID. +- 3.24 diverse routing of go & return:** Bidirectional transport entity/signal (i.e. go and return) is set up on/routed over different physical facilities. Such routing may apply to individual trails, subnetwork connections, or signals. This is illustrated in Figure 3-2. +- 3.25 diverse routing of [trail/SNC] protection pair:** Diverse routing of a working trail/SNC and its associated protection trail/SNC – where the working trail/SNC (in both directions of transmission) takes one (physical) route, and the protection trail/SNC (in both directions of transmission) takes another. +- 3.26 drop traffic:** Normal or extra traffic extracted from working, protection, or non-pre-emptible unprotected channels on the ring at a ring node. +- 3.27 externally initiated command:** An APS request that is initiated by either an OS or a craftsperson. +- 3.28 extra traffic:** Traffic that is carried over the protection channels when that capacity is not used for the protection of normal traffic. Extra traffic is not protected. Whenever the protection channels are required to protect the normal traffic, the extra traffic is pre-empted. +- 3.29 full pass-through:** The action of transmitting the same K1, K2, and protection channels that are being received. Full pass-through may be either unidirectional or bidirectional as specified in the text. When a node enters unidirectional full pass-through, it shall continue sourcing the previously sourced K-bytes in the opposite direction, with the exception that K2 bits 6-8 shall reflect the appropriate status code. +- 3.30 head-end:** The node executing a bridge. Note that a node functions as a head-end and as a tail-end for a bidirectional switch for the same span. +- 3.31 higher order virtual container:** See Recommendation G.707. +- 3.32 hold-off time:** The time between declaration of signal degrade or signal fail, and the initialization of the protection switching algorithm. +- 3.33 idle:** A node that is not generating, detecting, or passing-through bridge requests or bridge request status information. +- 3.34 isolated node:** A single node that is isolated from a traffic perspective by ring switches on each of its two spans by its adjacent nodes. +- 3.35 K-byte pass-through:** The action of transmitting the same K1 and K2 bytes that are being received. Protection channels are not passed through. K-byte pass-through is bidirectional. +- 3.36 long path:** The path segment away from the span for which the bridge request is initiated. Typically there are other intermediate nodes along this path segment. +- 3.37 Loss Of Frame (LOF):** See Recommendation G.783. +- 3.38 Loss Of Signal (LOS):** See Recommendation G.783 for SDH systems, and G.775 for PDH systems. + +- 3.39 lower order virtual container:** See Recommendation G.707. +- 3.40 lower order VC access:** The termination of a higher order VC for the purpose of adding, dropping, or cross-connecting any individual lower order VC or VC group. +- 3.41 misconnection:** A condition in which traffic destined for a given node is incorrectly routed to another node and no corrective action has been taken. +- 3.42 most significant bit:** The "leftmost" bit position, or first transmitted bit position in a byte. +- 3.43 Multiplex Section (MS):** See Recommendation G.803. +- 3.44 Multiplex Section Alarm Indication Signal (MS-AIS):** See Recommendation G.783. +- 3.45 Multiplex Section Remote Defect Indication (MS-RDI):** Formerly known as multiplex section far end remote failure. See Recommendation G.707. +- 3.46 network connection protection:** A scheme that protects the largest possible subnetwork connection of a trail. +- 3.47 network node interface (NNI):** See Recommendation G.707. +- 3.48 non-pre-emptible unprotected channel:** A channel in a MS shared protection ring provisioned bidirectionally to provide transport without MS shared protection ring automatic protection switching. Non-pre-emptible unprotected channels are provisioned from (corresponding) working and protection channel pairs. +- 3.49 non-pre-emptible unprotected traffic:** Unprotected traffic carried on protection locked-out channel which may not be pre-empted (e.g. by protection switches). +- 3.50 normal traffic:** Traffic that is normally carried in the working channels/sections, except in the event of a protection switch, in which case it is restored on the protection channels/sections. Normal traffic is protected. +- 3.51 null signal:** The null signal is indicated on the protection channels if they are not used to carry normal or extra traffic. The null signal can be any kind of signal that conforms to the signal structure of the specific layer and is ignored (not selected) at the tail-end of the protection. +- 3.52 pass-through:** The action of transmitting the same information that is being received for any given direction of transmission. +- 3.53 path:** See Recommendation G.803. +- 3.54 path overhead:** See Recommendation G.707. +- 3.55 protection channels:** The channels allocated to transport the normal traffic during a switch event. Protection channels may be used to carry extra traffic in the absence of a switch event. When there is a switch event, normal traffic on the affected working channels is bridged onto on the protection channels. +- 3.56 regenerator section:** See Recommendation G.803. +- 3.57 remote error indication:** Formerly far-end block error. See Recommendation G.707. +- 3.58 restoral threshold:** For automatically initiated commands, a hysteresis method is used when switching normal traffic from the protection channels back to the working channels. This method specifies a BER threshold for the multiplex section that is carrying the working channels. This threshold is commonly referred to as "restoral threshold". The restoral threshold is set to a lower BER than the signal degrade threshold. +- 3.59 restoration:** See Recommendation G.803. + +- 3.60 ring:** A collection of nodes forming a closed loop whereby each node is connected to two adjacent nodes via a duplex communications facility. A ring provides redundant bandwidth or redundant network equipment, or both, so distributed services can be automatically restored following a failure or degradation in the network. Thus, a ring can be self-healing. +- 3.61 ring failure:** A failure for which restoration can only be accomplished by a ring switch. +- 3.62 ring interworking:** A network topology where two rings are connected at two points and operate such that failure at either of these two points will not cause loss of any traffic, except possibly that dropped or inserted at the point of failure. +- 3.63 ring switching:** Protection mechanism that applies to both two-fibre and four-fibre rings. During a ring switch, the traffic from the affected span is carried over the protection channels on the long path. +- 3.64 section overhead:** See Recommendation G.707. +- 3.65 segmented ring:** A ring that is separated into two or more segments, either externally using Forced Switches (FS-R), or automatically as a result of Signal Failed - Ring switches (SF-R). +- 3.66 shared protection:** A protection architecture using $m$ protection entities shared among $n$ working entities ( $m:n$ ). The protection entities may also be used to carry extra traffic when not used for protection. See Recommendation G.803. +- 3.67 short path:** The path segment over the span for which the bridge request is initiated. This span is always the one to which both the head-end and tail-end are connected. The short path bridge request is the bridge request sent over the span for which the bridge request is initiated. +- 3.68 single point failure:** Failure located at a single physical point in a ring. The failure may affect one or more fibres. A single point failure may be detected by any number of NEs. +- 3.69 span:** The set of multiplex sections between two adjacent nodes on a ring. +- 3.70 span switching:** Protection mechanism similar to 1:1 linear APS that applies only to four-fibre rings where working and protection channels are contained in separate fibres and the failure only affects the working channels. During a span switch, the normal traffic is carried over the protection channels on the same span as the failure. +- 3.71 squelched traffic:** An all "1"s signal resulting from the squelching process. +- 3.72 squelching:** The process of inserting AU-AIS in order to prevent misconnections. +- 3.73 subnetwork connection:** See Recommendation G.803. +- 3.74 subnetwork connection protection:** A working subnetwork connection is replaced by a protection subnetwork connection if the working subnetwork connection fails, or if its performance falls below a required level. +- 3.75 survivable network:** A network that is capable of restoring traffic in the event of a failure. The degree of survivability is determined by the network's ability to survive single line system failures, multiple line system failures, and equipment failures. +- 3.76 switch:** The action of selecting normal traffic from the protection channels rather than the working channels. +- 3.77 switch completion time:** The interval from the decision to switch to the completion of the bridge and switch operation at a switching node initiating the bridge request. +- 3.78 switching node:** The node that performs the bridge or switch function for a protection event. In the case of a multiplex section switched ring network architecture, this node also performs any necessary squelching of misconnected traffic for VC-3/4 or higher rate paths. + +- 3.79 synchronous:** The essential characteristic of time scales or signals such that their corresponding significant instants occur at precisely the same average rate. +- 3.80 Synchronous Transport Module level N (STM-N):** See Recommendation G.707. +- 3.81 tail-end:** The node that is requesting the bridge. Note that a node functions as a head-end and a tail-end for a bidirectional switch for the same span. +- 3.82 Time Slot Interchange (TSI):** For purposes of this Recommendation, TSI is the capability of changing the time slot position of through-connected traffic (i.e. traffic that is not added or dropped from the node). +- 3.83 trail:** See Recommendation G.803. +- 3.84 trail protection:** Normal traffic is carried over/selected from a protection trail instead of a working trail if the working trail fails, or if its performance falls below a required level. +- 3.85 transport:** Facilities associated with the carriage of STM-1 or higher level signals. +- 3.86 undetected failure:** Any equipment defect which is not detected by equipment maintenance functions, hence does not initiate a protection switch or provide the appropriate OA&M notification. These types of failures do not manifest themselves until a protection switch is attempted. +- 3.87 unidirectional connection:** See Recommendation G.803. An illustration is given in Figure 3-1. +- 3.88 unidirectional protection switching:** A protection switching architecture in which, for a unidirectional failure (i.e. a failure affecting only one direction of transmission), only the affected direction (of the "trail", "subnetwork connection", etc.) is switched to protection. +- 3.89 unidirectional ring:** In a unidirectional ring (path switched or multiplex section switched), normal routing of the normal traffic is such that both directions of a bidirectional connection travel around the ring in the same direction (e.g. clockwise). Specifically, each bidirectional connection uses capacity along the entire circumference of the ring. +- 3.90 uniform routing of go & return:** Bidirectional transport entity/signal (i.e. go and return) is set up on/routed over the same physical facilities. Such routing may apply to individual trails, subnetwork connections, or signals. This is illustrated in Figure 3-2. +- 3.91 virtual container (VC):** See Recommendation G.707. +- 3.92 working channels:** The channels over which normal traffic is transported when there are no switch events. + + + +The diagram illustrates a unidirectional connection. On the left is a cloud-like shape with a scalloped border. Two curved arrows originate from this cloud. The upper arrow points to a rectangular box labeled 'A' above it. The lower arrow points to a rectangular box labeled 'B' above it. Both arrows have a small arrowhead near the cloud, indicating the direction of the connection away from the cloud. Below box 'B', there is a small downward-pointing arrow and the text 'T1516660-94'. + +Diagram of a unidirectional connection between a cloud and two nodes, A and B. + +**Figure 3-1/G.841 – Unidirectional connection** + + + +The traffic shares the same equipment and link + +a) Uniformly routed + +The traffic is on different equipment and links + +b) Diversely routed + +T1516670-94 + +Two diagrams illustrating network routing. Diagram (a) shows 'Uniformly routed' traffic where all paths share the same equipment and link. Diagram (b) shows 'Diversely routed' traffic where paths use different equipment and links. Both diagrams include nodes A and B, and cloud-like shapes representing network segments. Arrows indicate the direction of traffic flow. + +**Figure 3-2/G.841 – Uniformly routed and diversely routed bidirectional connection** + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|---------|-----------------------------------------------------| +| ADM | Add/Drop Multiplex | +| AIS | Alarm Indication Signal | +| AP | Access Point | +| APS | Automatic Protection Switching | +| AU | Administrative Unit | +| AUG | Administrative Unit Group | +| AU-AIS | Administrative Unit Alarm Indication Signal | +| AU-LOP | Administrative Unit Loss of Pointer | +| BER | Bit Error Ratio | +| BIP-N | Bit Interleaved Parity N | +| BLSR | Bidirectional Line Switched Rings | +| Br | Bridge(d) | +| CP | Connection Point | +| DCC | Data Communications Channel | +| DCN | Data Communications Network | +| ET | Extra Traffic | +| EXER-R | Excerciser - Ring | +| EXER-S | Excerciser - Span | +| FS-P | Forced Switch to Protection | +| FS-R | Forced Switched Normal Traffic to Protection - Ring | +| FS-S | Forced Switched Normal Traffic to Protection - Span | +| FS-W | Forced Switch Normal Traffic to Working | +| HO | Higher Order | +| HO VC | Higher Order Virtual Container | +| HP-DEG | Higher Order Path Degraded | +| HP-EXC | Higher Order Path Excessive Errors | +| HP-SSF | Higher Order Path Server Signal Fail | +| HP-TIM | Higher Order Path Trace Identifier Mismatch | +| HP-UNEQ | Higher Order Path Unequipped | +| ID | Identification | +| LO | Lower Order | +| LOF | Loss Of Frame | +| LO VC | Lower Order Virtual Container | +| LP | Lockout of Protection | + +| | | +|---------|--------------------------------------------------------| +| LP-DEG | Lower Order Path Degraded | +| LP-EXC | Lower Order Path Excessive Errors | +| LP-S | Lockout of Protection - Span | +| LP-SSF | Lower Order Path Server Signal Fail | +| LP-TIM | Lower Order Path Trace Identifier Mismatch | +| LP-UNEQ | Lower Order Path Unequipped | +| LOS | Loss Of Signal | +| MS | Multiplex Section | +| MSA | Multiplex Section Adaptation | +| MSP | Multiplex Section Protection | +| MSPA | Multiplex Section Protection Adaptation | +| MSPT | Multiplex Section Protection Termination | +| MST | Multiplex Section Termination | +| MS-P | Manual Switch to Protection | +| MS-R | Manual Switch Normal Traffic to Protection - Ring | +| MS-S | Manual Switch Normal Traffic to Protection - Span | +| MS-W | Manual Switch Normal Traffic to Working | +| NE | Network Element | +| NNI | Network Node Interface | +| NR | No Request | +| NUT | Non-pre-emptible unprotected traffic | +| OAM&P | Operations, Administration, Maintenance & Provisioning | +| OS | Operation System(s) | +| POH | Path OverHead | +| RR-R | Reverse Request - Ring | +| RR-S | Reverse Request - Span | +| RSOH | Regenerator Section OverHead | +| SD | Signal Degrade | +| SDH | Synchronous Digital Hierarchy | +| SD-P | Signal Degrade of the Protection Channels | +| SD-R | Signal Degrade - Ring | +| SD-S | Signal Degrade - Span | +| SF | Signal Fail | +| SF-R | Signal Fail - Ring | +| SF-S | Signal Fail - Span | +| SNC | SubNetwork Connection | + +| | | +|-------|----------------------------------------------------------------| +| SNC/I | SubNetwork Connection Protection with Inherent Monitoring | +| SNC/N | SubNetwork Connection Protection with Non-intrusive Monitoring | +| SSF | Server Signal Fail | +| STM-N | Synchronous Transport Module Level N | +| Sw | Switch(ed) | +| TCP | Termination Connection Point | +| TMN | Telecommunications Management Network | +| TSI | Time-Slot Interchange | +| TU | Tributary Unit | +| VC | Virtual Container | +| WTR | Wait To Restore | + +# 5 Protection classifications + +This clause describes in general terms the types of protection architectures described within this Recommendation. There are basically two types of protection switching: SDH trail protection and SDH subnetwork connection protection. + +MS shared protection rings is an SDH trail protection. Figure 5-1 illustrates the model of a two-fibre MS shared protection ring with a 4 AUG capacity, including the transmit and receive subnetwork connections. Figure 5-2 shows the same model reacting to a complete cable cut on one side. Figure 5-3 shows the same model reacting as a pass-through node. + +Figure 5-4 shows the generic functional model for 1 + 1 VC trail protection. Figure 5-5 shows the generic functional model for 1:1 revertive VC trail protection and Figure 5-6 shows the generic functional model for 1:1 non-revertive VC trail protection. + +Figure 5-7 shows the functional model for subnetwork connection protection with inherent monitoring (SNC/I). Figure 5-8 shows the functional model for subnetwork connection with non-intrusive monitoring (SNC/N). + + + +The diagram illustrates the functional model for a two-fibre protection ring in a normal state with extra traffic. At the top, an oval labeled 'HPC' (Higher order Path Connection) is connected via multiple bidirectional arrows to a row of 'MSA' (Multiplex Section Adaptation) blocks. Each 'MSA' block is paired with an 'MSPT' (Multiplex Section Protection Termination) block below it. These 'MSPT' blocks are connected to a large central oval labeled 'MSPC' (Multiplex Section Protection Connection). Below the 'MSPC' oval, there are two 'MSPA' (Multiplex Section Protection Adaptation) blocks on the left and two on the right. Each 'MSPA' block is connected to an 'MST' (Multiplex Section Termination) block. The 'MST' blocks on the left converge to 'STM-4 West', and those on the right converge to 'STM-4 East'. External commands enter the left side of the MSPC. On the right side, a 'Squelch table' and a 'Node ID table' provide input to the MSPC. A legend defines traffic types: Working (white), Extra traffic (dark grey), and Protection (light grey). The text 'T1516680-94' is in the bottom right. + +- Working +- Extra traffic +- Protection + +- HPC Higher order Path Connection +- MSA Multiplex Section Adaptation +- MSPA Multiplex Section Protection Adaptation +- MSPC Multiplex Section Protection Connection +- MSPT Multiplex Section Protection Termination +- MST Multiplex Section Termination + +Functional model for a two-fibre protection ring showing traffic paths (Working, Extra traffic, Protection) between HPC, MSA, MSPT, MSPC, MSPA, and MST components, with STM-4 West and STM-4 East interfaces. + +**Figure 5-1/G.841 – Functional model for a two-fibre protection ring – +Normal state with extra traffic** + + + +Working +Extra traffic +Protection + +HPC Higher order Path Connection +MSA Multiplex Section Adaptation +MSPA Multiplex Section Protection Adaptation +MSPC Multiplex Section Protection Connection +MSPT Multiplex Section Protection Termination +MST Multiplex Section Termination + +Functional model for a two-fibre MS shared protection ring showing a failure on the east side. The diagram consists of an upper HPC (Higher order Path Connection) layer connected via multiple MSA (Multiplex Section Adaptation) and MSPT (Multiplex Section Protection Termination) blocks to a central MSPC (Multiplex Section Protection Connection) ring. Below the MSPC, MSPA (Multiplex Section Protection Adaptation) and MST (Multiplex Section Termination) blocks connect to STM-4 West and STM-4 East interfaces. The STM-4 East interface has a large 'X' across its lines, indicating a failure. External commands, a Squelch table, and a Node ID table are shown as external inputs. A legend identifies Working (white), Extra traffic (dark grey), and Protection (light grey) paths. Legend + +**Figure 5-2/G.841 – Functional model for a two-fibre MS shared protection ring – +Failure on east side** + + + +HPC + MSA + MS PT + MSPC + External commands + MSPA + MST + STM-4 West + STM-4 East + Squelch table + Node ID table + T1516700-94 + +Working + Extra traffic + Protection + +HPC Higher order Path Connection + MSA Multiplex Section Adaptation + MSPA Multiplex Section Protection Adaptation + MSPC Multiplex Section Protection Connection + MSPT Multiplex Section Protection Termination + MST Multiplex Section Termination + +Functional model for a two-fibre MS shared protection ring in pass-through state. The diagram shows a central MSPC (Multiplex Section Protection Connection) ring connected to multiple STM-4 West and STM-4 East interfaces via MST (Multiplex Section Termination) and MSPA (Multiplex Section Protection Adaptation) components. Above the MSPC ring, there are multiple MSPT (Multiplex Section Protection Termination) and MSA (Multiplex Section Adaptation) components. The HPC (Higher order Path Connection) is shown at the top, connected to the MSA components. The diagram uses different shading to indicate Working (white), Extra traffic (dark grey), and Protection (light grey) paths. External commands, Squelch table, and Node ID table are also shown as inputs to the MSPA components. + +**Figure 5-3/G.841 – Functional model for a two-fibre MS shared protection ring – Pass-through state** + + + +The diagram illustrates the functional model for generic 1 + 1 linear trail protection across two nodes. At the top, each node has an 'Adaptation' (A) block. Below it is a 'Protection Trail Termination' (TTp) block. A 'Protected trail' is shown as a dashed line connecting the two A blocks. Below TTp is a 'Protection Matrix Connection' (MCp) represented by an oval with four ports labeled 1, 2, W, and P. 'External commands' are indicated by dotted lines pointing to the MCp ovals. Below the MCp are four 'Protection Adaptation' (Ap) blocks. Signal flow is indicated by arrows, with labels for 'Signal Fail' (SF), 'Signal Degrade' (SD), and 'APS\*' (Automatic Protection Switching). Below the Ap blocks are 'Trail Termination' (TT) blocks. 'Remote Defect Indication' (RDI) and 'Remote Error Indication' (REI) signals are shown between TT blocks. At the bottom, 'Protection Network Connection' (NCp) and 'Working Network Connection' (NCw) are shown as dashed lines connecting the two nodes. The label 'T1516710-94' is in the bottom right corner. + +Functional model for generic 1 + 1 linear trail protection diagram showing two nodes with Protection Matrix Connections (MCp), Adaptation (A), Protection Trail (Trailp), and Working Trail (Trailw) components. + +\* Required for dual-ended switching. + Not required for single-ended switching. + +- | | | | | +|-----------------|-------------------------------|--------------------|------------------------------| +| A | Adaptation | SD | Signal Degrade | +| A p | Protection Adaptation | SF | Signal Fail | +| MC p | Protection Matrix Connection | SSF | Server Signal Fail | +| NC p | Protection Network Connection | Trail p | Protection Trail | +| NC w | Working Network Connection | Trail w | Working Trail | +| RDI | Remote Defect Indication | TT | Trail Termination | +| REI | Remote Error Indication | TT p | Protection Trail Termination | + +States: 1 Normal state + 2 Failure state + +**Figure 5-4/G.841 – Functional model for generic 1 + 1 linear trail protection** + + + +Functional model for generic 1:1 linear trail protection – Revertive operation diagram. The diagram shows two identical nodes connected by a 'Protected trail'. Each node consists of four 'Adaptation' (A) blocks at the top, four 'Protection Trail Termination' (TTp) blocks below them, a central 'Protection Matrix Connection' (MCp) represented by an oval with internal switches, four 'Protection Adaptation' (Ap) blocks below the matrix, and four 'Trail Termination' (TT) blocks at the bottom. Traffic flows are shown: 'Extra traffic' and 'Normal traffic' entering/leaving the A blocks; signals passing through TTp to MCp, then through Ap to TT. Control signals like SSF\*, MCp, APS, SF, SD, RDI, and REI are indicated between components. At the bottom, 'Working Trail' (Trailw) and 'Protection Network Connection' (NCp, NCw) paths are shown between the TT blocks. A label 'T1516720-94' is at the bottom right. + +\* SSF active on open connection [Failure state (2)]. This is for further study. + +| | | | | +|-----------------|-------------------------------|--------------------|------------------------------| +| A | Adaptation | SD | Signal Degrade | +| A p | Protection Adaptation | SF | Signal Fail | +| MC p | Protection Matrix Connection | SSF | Server Signal Fail | +| NC p | Protection Network Connection | Trail p | Protection Trail | +| NC w | Working Network Connection | Trail w | Working Trail | +| RDI | Remote Defect Indication | TT | Trail Termination | +| REI | Remote Error Indication | TT p | Protection Trail Termination | + +States: 1 Normal state +2 Failure state + +**Figure 5-5/G.841 – Functional model for generic 1:1 linear trail protection – Revertive operation** + + + +Functional model for generic 1:1 linear trail protection – Non-revertive operation. The diagram shows two identical nodes connected by a 'Protected trail'. Each node consists of four 'A' (Adaptation) blocks at the top, four 'TT\_p' (Protection Trail Termination) blocks below them, a central 'MC\_p' (Protection Matrix Connection) oval, four 'A\_p' (Protection Adaptation) blocks below the matrix, and four 'TT' (Trail Termination) blocks at the bottom. External traffic (Extra and Normal) enters the 'A' blocks. Signals flow from 'A' to 'TT\_p', then through the 'MC\_p' matrix (with states 1 and 2), then through 'A\_p' to 'TT'. Control signals like SF, SD, APS, RDI, and REI are shown between components. At the bottom, 'Trail\_p\*', 'Trail\_w\*', 'NC\_p\*', and 'NC\_w\*' connections are indicated between the two nodes. A note at the bottom right reads T1516730-94. + +\* On failure state (2), Trailp becomes Trailw, Trailw becomes Trailp, NCp becomes NCw, and NCw becomes NCp. + +| | | | | +|-----------------|-------------------------------|--------------------|------------------------------| +| A | Adaptation | SD | Signal Degrade | +| A p | Protection Adaptation | SF | Signal Fail | +| MC p | Protection Matrix Connection | SSF | Server Signal Fail | +| NC p | Protection Network Connection | Trail p | Protection Trail | +| NC w | Working Network Connection | Trail w | Working Trail | +| RDI | Remote Defect Indication | TT | Trail Termination | +| REI | Remote Error Indication | TT p | Protection Trail Termination | + +States: 1 Normal state +2 Failure state + +**Figure 5-6/G.841 – Functional model for generic 1:1 linear trail protection – Non-revertive operation** + + + +Functional model for Subnetwork Connection Protection with Inherent Monitoring (SNC/I) by means of a server signal fail. The diagram shows two client layers connected to a server layer via adaptation (A) and trail termination (TT) units. Each client layer contains a matrix connection (MC) with ports 1 and 2, and states 1 (Normal) and 2 (Failure). The server layer includes protection (P) and working (W) subnetwork connections (SNCp, SNCw) and server signal fail (SSF) indicators. Arrows show data flow from client to server and back, with SSF signals being monitored for failure detection. + +- A Adaptation + - MC Matrix Connection + - SNCp Protection Subnetwork Connection + - SNCw Working Subnetwork Connection + - SSF Server Signal Fail + - TT Trail Termination +- States: 1 Normal state +2 Failure state + +**Figure 5-7/G.841 – Functional model for Subnetwork Connection Protection with Inherent Monitoring (SNC/I) by means of a server signal fail** + + + +The diagram illustrates the functional model for Subnetwork Connection Protection with Non-intrusive Monitoring (SNC/N). It shows two parallel subnetwork connection paths, one for the working subnetwork connection (SNCw) and one for the protection subnetwork connection (SNCp). + +At the top, a dashed line labeled "Protected subnetwork connection" spans both paths. Below this, "External commands" are shown entering the system. The diagram is divided into three layers by horizontal dashed lines: "Client layer" at the top, "Server layer" in the middle, and an unlabeled bottom section. + +In the Client layer, each path has a Matrix Connection (MC) node with four ports labeled 1, 2, P, and MC. Port 1 is connected to a Working (W) node, port 2 to a Protection (P) node, port P to another Working (W) node, and port MC to a Protection Matrix Connection (MCp) node. The MCp node is connected to the Server layer via a Server Signal Fail (SSF) node. + +In the Server layer, each path has four Adaptation (A) nodes. The first A node is connected to the MC node, the second to the W node, the third to the P node, and the fourth to the MCp node. Each A node is connected to a Trail Termination (TT) node below it. The TT nodes are interconnected with the SNCw and SNCp lines at the bottom. + +Monitoring is implemented using Non-intrusive Monitors (TTm). These are connected to the W and P nodes in the Client layer and to the A nodes in the Server layer. Signal Fail (SF) and Signal Degrade (SD) signals are shown being passed between the Client layer and the TTm nodes. + +States are indicated by numbers 1 (Normal state) and 2 (Failure state) next to the MC nodes. + +Functional model for Subnetwork Connection Protection with Non-intrusive Monitoring (SNC/N). + +- A Adaptation +- MC Matrix Connection +- MCp Protection Matrix Connection +- SD Signal Degrade +- SF Signal Fail +- SNCp Protection Subnetwork Connection +- SNCw Working Subnetwork Connection +- SSF Server Signal Fail +- TT Trail Termination +- TTm Non-intrusive Monitor + +States: 1 Normal state +2 Failure state + +**Figure 5-8/G.841 – Functional model for Subnetwork Connection Protection with Non-intrusive Monitoring (SNC/N)** + +# 6 Applications considerations + +This clause describes in general terms some of the possible advantages to be gained by the various protection architectures. + +## 6.1 MS shared protection rings + +MS shared protection rings can be categorized into two types: two-fibre and four-fibre. The ring APS protocol accommodates both types. + +For MS shared protection rings, the working channels carry the normal traffic signals to be protected while the protection channels are reserved for protection of this service. Protection channels may be used to carry extra traffic when not being used for protection of normal traffic. Normal traffic signals are transported bidirectionally over spans: an incoming tributary travels in one direction of the working channels while its associated outgoing tributary travels in the opposite direction but over the same spans. + +The pair of tributaries (incoming and outgoing) only uses capacity along the spans between the nodes where the pair is added and dropped. Thus, as illustrated in Figure 6-1, the pattern that these pairs of tributaries are placed on the ring impacts the maximum load that can be placed on MS shared protection rings. The sum of the tributaries that traverse a span cannot exceed the maximum capacity of that particular span. + +Depending upon the tributary pattern, the maximum load that can be placed on a (bidirectional) MS shared protection ring can exceed the maximum load that can be placed on the equivalent type of unidirectional ring (e.g. MS dedicated protection, or SNC protection) with the same optical rate and the same number of fibres. This gives the bidirectional ring a capacity advantage over unidirectional rings, except whenever the tributaries are all destined for only one node on the ring, in which case they are equivalent. + +One advantage of MS shared protection rings is that service can be routed on the ring in either one of the two different directions, the long way around the ring or the short way. Although the short way will usually be preferred, occasionally routing service over the long way permits some load balancing capabilities. + +When the protection channels are not being used to restore the normal traffic signals, they can be used to carry extra traffic signals. In the event of a protection switch, the normal traffic on the working channels will access the protection channels causing any extra traffic to be removed from the protection channels. + +During a ring switch, normal traffic transmitted toward the failed span is switched at one switching node to the protection channels transmitted in the opposite direction (away from the failure). This bridged traffic travels the long way around the ring on the protection channels to the other switching node where the normal traffic from the protection channels are switched back onto the working channels. In the other direction, the normal traffic is bridged and switched in the same manner. Figure 6-2 illustrates a ring switch in response to a cable cut. + +During a ring switch, the failed span is effectively "replaced" with the protection channels between the switching nodes, travelling the long way around the ring. Since the protection channels along each span (except the failed span) are used for recovery, the protection capacity is effectively shared by all spans. + +MS SPRING protocols allow the available bandwidth to be partitioned into three types of channels: working channel to carry normal traffic, protection channel which may be used to carry extra traffic, and NUT channel to carry non-pre-emptible unprotected traffic. Normal traffic is protected against failure events via the MS SPRING APS protocol, while extra traffic is unprotected traffic carried on + +the protection channels. Any failure event that may require the protection channels for protection purposes shall pre-empt the extra traffic. + +Non-pre-emptible unprotected traffic is unprotected traffic that is carried on channels with the MS SPRING APS protection switching mechanism disabled for certain HO VC channels (i.e. working channels and their corresponding protection channels). Traffic carried on these channels is unprotected and non-pre-emptible. Thus, NUT carried on non-pre-emptible unprotected channels afford a higher level of survivability as compared to extra traffic, but lower level of survivability as compared to normal traffic. + +Examples of how NUT channels can be used are given in Figures 6-3 and 6-4: + +- Figure 6-3 shows a logical ring in which SNCP is used as a protection mechanism partially embedded in an MS SPRING using NUT. This arrangement avoids unnecessary layering of protection mechanisms and is more bandwidth efficient than the same application without NUT. +- Figure 6-4 shows a similar application, this time with the NUT channels supporting HO VC connectivity among ATM switches. Under the assumption that the ATM traffic is protected by other means or does not need to be protected, this application of NUT has the same advantages as the previous example. + + + +Two-fibre STM-16 ring + +Node A + +Node B + +Node D + +Node C + +8 AU-4s + +6 AU-4s + +2 AU-4s + +16 AU-4s total + +Spans between nodes A & B and nodes A & D are at capacity + +Diagram of a two-fibre STM-16 ring with four nodes (A, B, C, D). Node A is at the top left, B at top right, C at bottom right, and D at bottom left. The ring is labeled 'Two-fibre STM-16 ring'. Traffic is indicated by arrows and AU-4s values: 8 AU-4s between A and B, 6 AU-4s between A and D, 2 AU-4s between D and C, and 16 AU-4s total. A note states: 'Spans between nodes A & B and nodes A & D are at capacity'. + +NOTE – Since all the traffic is destined for node A, and the span between node A and node B is full, traffic from node C routes through node D, leaving the span between node B and node C vacant. + +a) All traffic destined for one node, Node A + + + +Two-fibre STM-16 ring + +Node A + +Node B + +Node D + +Node C + +8 AU-4s + +8 AU-4s + +8 AU-4s + +32 AU-4s total + +All spans are at capacity + +Diagram of a two-fibre STM-16 ring with four nodes (A, B, C, D) showing all traffic destined for Node A. Traffic values: 8 AU-4s between A and B, 8 AU-4s between A and D, 8 AU-4s between D and C, and 32 AU-4s total. A note states: 'All spans are at capacity'. + +b) All traffic destined for adjacent nodes only + + + +Two-fibre STM-16 ring + +Node A + +Node B + +Node D + +Node C + +2 AU-4s + +3 AU-4s + +4 AU-4s + +5 AU-4s + +22 AU-4s total + +All spans are at capacity + +T1516760-94 + +Diagram of a two-fibre STM-16 ring with four nodes (A, B, C, D) showing mixed traffic patterns. Traffic values: 2 AU-4s between A and B, 3 AU-4s between A and D, 4 AU-4s between D and C, 5 AU-4s between B and C, and 22 AU-4s total. A note states: 'All spans are at capacity'. Reference T1516760-94 is shown. + +c) Mixed traffic pattern + +**Figure 6-1/G.841 – Effects of demand pattern on capacity of bidirectional MS shared protection rings** + + + +Diagram (a) Normal state: A ring network of six nodes (A, B, C, D, E, F). Node A is top-left, B is top-center, C is top-right, D is bottom-right, E is bottom-center, and F is bottom-left. Each node is connected to its neighbors by two paths: a thick grey 'Working' path and a thin white 'Protection' path. Circuit Q enters Node A from above, travels along the working path through Node B to Node C, and then down to Node D where it exits downwards. + +a) Normal state + + + +Diagram (b) Failed state: The same ring network as above, but with a large 'X' indicating a failure on the working path between Node B and Node C. Circuit Q enters Node A. Because of the failure, the circuit is rerouted at Node B. It loops back onto the protection path, traveling from Node B through Node A, Node F, Node E, and Node D to reach Node C. From Node C, it exits at Node D as in the normal state. + +b) Failed state + +T1516770-94 + + + +| | | +|--|------------------------------| +| | Working | +| | Protection | +| | Circuit transporting service | + +Thick grey rectangle symbol Thin white rectangle symbol Double-headed arrow symbol + +**Figure 6-2/G.841 – Example of circuit routing in failure state for a ring switch** + + + +The diagram illustrates a logical ring configuration. It features several nodes represented by ovals and rectangles. Two large ovals at the top contain 'SNCP' and 'MS SPRING' blocks, each with two STM-16 link icons. These are connected via a central STM-16 link. Below them, two more ovals contain 'MS SPRING' blocks, each with two STM-16 link icons, connected to the top nodes via STM-16 links. At the bottom, an oval contains an 'SNCP' block connected to the middle 'MS SPRING' node via two STM-1 links. A legend at the bottom left shows an STM-16 link icon (two arrows) and an STM-1 link icon (one arrow). + +T1529630-98 + +STM-16 + +STM-1 + +Diagram of a logical ring showing SNCP and MS SPRING protection mechanisms. The diagram includes nodes for SNCP and MS SPRING connected by STM-16 and STM-1 links. A legend at the bottom left identifies the link types. + +**Figure 6-3/G.841 – Logical ring in which SNCP is used as a protection mechanism partially embedded in an MS shared protection ring** + + + +The diagram shows a network topology with four ATM Switches and five MS SPRING nodes. The ATM switches are arranged in a mesh-like fashion, with two at the top and two at the bottom. The MS SPRING nodes are positioned between the ATM switches. Connections between nodes are marked with arrows indicating the type of STM channel: a single arrow for STM-16 and a double arrow for STM-1. A legend at the bottom left shows a single arrow labeled 'STM-16' and a double arrow labeled 'STM-1'. A small text label 'T1529640-98' is present in the lower right area of the diagram. + +Diagram showing NUT Channels supporting HO VC connectivity among ATM switches. The diagram illustrates a network of ATM switches and MS SPRING nodes connected by STM-16 and STM-1 channels. A legend at the bottom left identifies the channel types by their arrow symbols: a single arrow for STM-16 and a double arrow for STM-1. + +**Figure 6-4/G.841 – NUT Channels supporting HO VC connectivity among ATM switches** + +## 6.2 MS shared protection rings (transoceanic application) + +This application, including its additional requirements and operating characteristics, are described in Annex A. + +## 6.3 MS dedicated protection rings + +An MS dedicated protection ring consists of two counter-rotating rings, each transmitting in opposite directions relative to each other. In this case, only one ring carries normal traffic to be protected while the other is reserved for protection of this normal traffic. + +The maximum demand that can be placed on the ring is limited to the capacity of a span. The pattern of the demand placed on the ring does not impact the capacity of unidirectional rings. In other words, the sum of the demand from all the nodes cannot exceed the capacity of a single span. + +MS dedicated protection rings would also require using the APS bytes, K1 and K2, for protection switching. + +## **6.4 Unidirectional and bidirectional protection switching** + +Possible advantages of unidirectional protection switching include: + +- 1) Unidirectional protection switching is a simple scheme to implement and does not require a protocol. +- 2) Unidirectional protection switching can be faster than bidirectional protection switching because it does not require a protocol. +- 3) Under multiple failure conditions there is a greater chance of restoring traffic by protection switching if unidirectional protection switching is used, than if bidirectional protection switching is used. + +Possible advantages of bidirectional protection switching when uniform routing is used include: + +- 1) With bidirectional protection switching operation, the same equipment is used for both directions of transmission after a failure. The number of breaks due to single failures will be less than if the path is delivered using the different equipment. +- 2) With bidirectional protection switching, if there is a fault in one path of the network, transmission of both paths between the affected nodes is switched to the alternative direction around the network. No traffic is then transmitted over the faulty section of the network and so it can be repaired without further protection switching. +- 3) Bidirectional protection switching is easier to manage because both directions of transmission use the same equipments along the full length of the trail. +- 4) Bidirectional protection switching maintains equal delays for both directions of transmission. This may be important where there is a significant imbalance in the length of the trails e.g. transoceanic links where one trail is via a satellite link and the other via a cable link. +- 5) Bidirectional protection switching also has the ability to carry extra traffic on the protection path. + +## **6.5 Linear VC trail protection** + +Linear VC trail protection is a dedicated protection mechanism that can be used on any physical structure (i.e. meshed, ring, or mixed). It may be applied in any path layer in a layered network. + +It is an end-to-end protection mechanism, and switches on server failures and client level information, including path performance information. It need not be used on all VCs within a multiplex section. + +Linear VC trail protection switching can operate in a unidirectional or bidirectional manner. Bidirectional protection switching has the ability to carry extra traffic on the protection path. + +## 6.6 Subnetwork connection protection + +Subnetwork connection protection is a dedicated protection mechanism that can be used on any physical structure (i.e. meshed, rings, or mixed). It may be applied at any path layer in a layered network. + +It can be used to protect a portion of a path (e.g. that portion where two separate paths segments are available) between two Connection Points (CPs) or between a CP and a Termination Connection Point (TCP), or the full end-to-end path between two TCPs. It switches on server failures (using inherent monitoring) or it switches using client layer information (using non-intrusive monitoring). + +SNC protection is a linear protection scheme which can be applied on an individual basis to VC-n signals. It need not be used on all VCs within a multiplex section. It need not be used on all LO VCs within a HO VC. + +The individual HO VCs [LO VCs] transported within the network may either be all unprotected, all 1 + 1 HO VC [LO VC] SNC/I protected, all 1 + 1 HO VC [LO VC] SNC/N protected, all HO VC [LO VC] trail protected (see 6.5), or a mixture of unprotected, 1 + 1 HO VC [LO VC] SNC/I protected, 1 + 1 HO VC [LO VC] SNC/N protected and HO VC [LO VC] trail protected. + +HO VCs [LO VCs] which are unprotected at their own HO [LO] path layer may be protected indirectly at their server layer; e.g. a HO VC signal in a MS Spring protected ring is protected against faults in the ring by means of MS Spring protection. + +On the other hand, client signals transported within an unprotected HO VC (e.g. LO VCs, ATM VPs) may be protected by means of their client layer protection schemes (e.g. LO VC SNC protection, ATM VP SNC protection). + +The decision to protect a signal and the actual protection type used are outside the scope of this Recommendation: this is determined by the network architecture and the quality of service needs. + +SNC protection operates in a unidirectional protection switching manner. The ability to perform bidirectional protection switching and the carriage of extra traffic is for further study. + +## 6.7 Linear multiplex section protection switching + +Linear multiplex section protection switching can be a dedicated or shared protection mechanism. It protects the multiplex section layer, and applies to point-to-point physical networks. One protection multiplex section can be used to protect the normal traffic from a number (N) of working multiplex sections. It cannot protect against node failures. It can operate in a unidirectional or bidirectional manner, and it can carry extra traffic on the protection multiplex section in bidirectional operation. + +# 7 SDH trail protection + +This clause describes the detailed equipment characteristics required to support SDH trail protection applications. + +## 7.1 Linear multiplex section protection + +This subclause describes the MSP protocol compatible with 1:n operation. Annex B describes the MSP protocol optimized for 1 + 1 non-revertive operation. + +### 7.1.1 MSP protocol + +The MSP functions, at the ends of a multiplex section, make requests for and give acknowledgements of switch action by using the APS bytes (K1 and K2 bytes in the MSOH of the protection section). The bit assignments for these bytes and the bit-oriented protocol are defined as follows. + +#### 7.1.1.1 K1 byte + +The K1 byte indicates a request of a traffic signal for switch action. + +Bits 1-4 indicate the type of request, as listed in Table 7-1. A request can be: + +- 1) a condition (SF and SD) associated with a section. A condition has high or low priority. The priority is set for each corresponding section; +- 2) a state (wait-to-restore, do not revert, no request, reverse request) of the MSP function; or +- 3) an external request (lockout of protection, forced or manual switch, and exercise). + +Bits 5-8 indicate the number of the traffic signal or section for which the request is issued, as shown in Table 7-2. + +**Table 7-1/G.841 – Types of request** + +| Bits | Condition, state or external request | Order
(Note 1) | +|----------------|--------------------------------------|-------------------| +| 1 2 3 4 | | | +| 1 1 1 1 | Lockout of protection (Note 2) | Highest | +| 1 1 1 0 | Forced switch | ↑ | +| 1 1 0 1 | Signal fail high priority | . | +| 1 1 0 0 | Signal fail low priority | . | +| 1 0 1 1 | Signal degrade high priority | . | +| 1 0 1 0 | Signal degrade low priority | . | +| 1 0 0 1 | Unused (Note 3) | . | +| 1 0 0 0 | Manual switch | . | +| 0 1 1 1 | Unused (Note 3) | . | +| 0 1 1 0 | Wait-to restore | . | +| 0 1 0 1 | Unused (Note 3) | . | +| 0 1 0 0 | Exercise | . | +| 0 0 1 1 | Unused (Note 3) | . | +| 0 0 1 0 | Reverse request | . | +| 0 0 0 1 | Do not revert | ↓ | +| 0 0 0 0 | No request | Lowest | + +NOTE 1 – An SF condition on the protection section is higher priority than any of the requests that would cause a normal traffic signal to be selected from the protection section. + +NOTE 2 – Only the null signal (0) is allowed with a Lockout of Protection request. + +NOTE 3 – Some network operators may use these codes for network specific purposes. The receiver shall be capable of ignoring these codes. + +NOTE 4 – Requests are selected from the table depending on the protection switching arrangements; i.e. in any particular case, only a subset of the requests may be required. + +**Table 7-2/G.841 – K1 traffic signal number** + +| Signal number | Requesting switch action | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Null signal (no normal or extra traffic signal). Conditions and associated priority (fixed high) apply to the protection section. | +| 1-14 | Normal traffic signal (1-14)
Conditions and associated priority (high or low) apply to the corresponding working sections.
For 1 + 1 only traffic signal 1 is applicable, with fixed high priority. 1 + 1 systems may treat (incorrect) low priority request received over the K-bytes as equivalent to the corresponding high priority request. | +| 15 | Extra traffic signal
Conditions are not applicable.
Exists only when provisioned in a 1:n architecture. | + +#### **7.1.1.2 K1 byte generation rules** + +Local SF and SD conditions, wait-to-restore or do-not-revert state and the external request are evaluated by a priority logic, based on the descending order of request priorities in Table 7-1. If local conditions (SF or SD) of the same level are detected on different sections at the same time, the condition with the lowest section number takes priority. Of these evaluated requests, the one of the highest priority replaces the current local request, only if it is of higher priority. + +Locally detected SF and SD conditions and externally initiated requests for normal traffic signals that have "lockout of normal traffic signal from protection" control command (see 7.1.1.2.2) applied to them are not evaluated during K1 byte generation. + +##### **7.1.1.2.1 In bidirectional operation** + +The priorities of the local request and the remote request on the received K1 byte are compared according to the descending order of priorities in Table 7-1. Note that a received reverse request or a remote request for a normal traffic signal that has a "lockout of normal traffic signal from protection" applied to it are not considered in the comparison. + +The sent K1 shall indicate: + +- a) a reverse request if the remote bridge request is for a traffic signal that is not locked out and; + - i) the remote request is of higher priority, or if + - ii) the requests are of the same level (and are higher priority than a no request) and the sent K1 byte already indicates reverse request, or if + - iii) the requests are of the same level (and are higher priority than a no request) and the sent K1 byte does not indicate reverse request and the remote request indicates a lower traffic signal number; +- b) the local request in all other cases. + +##### **7.1.1.2.2 In unidirectional operation** + +The sent K1 byte shall always indicate the local request. Therefore, reverse request is never indicated. + +#### 7.1.1.3 Revertive/non-revertive modes + +In revertive mode of operation, when the protection is no longer requested, i.e. the failed working section is no longer in SD or SF condition (and assuming no other requesting sections), a local wait-to-restore state shall be activated. Since this state becomes the highest in priority, it is indicated on the sent K1 byte, and maintains the normal traffic signal from the previously failed working section on the protection section. This state shall normally time out and become a no request null signal (0) [or no request extra traffic signal (15), if applicable]. The wait-to-restore timer deactivates earlier if the sent K1 byte no longer indicates wait-to-restore, i.e. when any request of higher priority pre-empts this state. + +In non-revertive mode of operation, applicable only to 1 + 1 architecture, when the failed working section is no longer in SD or SF condition, the selection of the normal traffic signal from protection is maintained by activating a do-not-revert state rather than a no-request state. + +Both wait-to-restore and do-not-revert requests in the sent K1 byte are normally acknowledged by a reverse request in the received K1 byte. However, no request is acknowledged by another No Request received. + +#### 7.1.1.4 K2 byte + +Bits 1-5 indicate the status of the bridge in the MSP switch (see Figure 7-1). Bits 6-8 are used for MS-AIS and MS-RDI indication (see Recommendation G.707). + + + +The diagram illustrates the internal switching mechanism of an MSP switch in a 1:n architecture. It consists of two main components: a 'Bridge' on the left and a 'Selector' on the right. + +Inputs on the left include: + +- 'Null signal (0)': A line that can be switched to the protection section output. + +- 'Normal traffic signal 1': A line that can be switched to Working section 1 output. + +- 'Normal traffic signal 2': A line that can be switched to Working section 2 output. + +- 'Extra traffic signal (15)': A line that can be switched to the protection section output. + +The 'Bridge' component contains four switches, each with a '0' (normally open) and '1' (normally closed) position. These switches connect the input signals to the 'Selector' component. + +The 'Selector' component has four corresponding switches that direct traffic from the Bridge to the outputs: + +- 'Working section 1': Receives traffic from Normal traffic signal 1 (position 1) or Null signal (position 0). + +- 'Working section 2': Receives traffic from Normal traffic signal 2 (position 1) or Null signal (position 0). + +- 'Protection section (0)': Receives traffic from Extra traffic signal (position 15), Normal traffic signal 1 (position 1), Normal traffic signal 2 (position 2), or Null signal (position 0). + +The diagram is labeled 'T1508800-92/d34' at the bottom right. + +Diagram of an MSP switch in 1:n architecture showing Bridge and Selector components with signal paths for Null signal (0), Normal traffic signal 1, Normal traffic signal 2, and Extra traffic signal (15) connecting to Working section 1, Working section 2, and Protection section (0). + +**Figure 7-1/G.841 – MSP switch – 1:n architecture (shown in released position)** + +NOTE – In some regional applications, when MS-RDI is not being generated, bits 6-8 are used to indicate the switching mode (i.e. unidirectional, using code 100, and bidirectional, using code 101). Such applications are outside the scope of this Recommendation. + +Bits 1-4 indicate a signal number, as shown in Table 7-3. Bit 5 indicates the type of the MSP architecture: set 1 indicates 1:n architecture and set 0 indicates 1 + 1 architecture. + +**Table 7-3/G.841 – K2 traffic signal number** + +| Traffic signal number | Indication | +|-----------------------|----------------------------------------------------------------------------------------| +| 0 | Null traffic signal | +| 1-14 | Normal traffic signal (1-14)
For 1 + 1, only normal traffic signal 1 is applicable. | +| 15 | Extra traffic signal
Exists only when provisioned in a 1:n architecture. | + +#### 7.1.1.5 K2 byte generation rules + +The sent K2 byte shall indicate in bits 1 to 4, for all architectures and operation modes, null signal (0) if the received K1 byte indicates null signal and the extra traffic is not bridged. For all other cases the number of the signal which is bridged shall be indicated by the sent K2 byte. + +The sent K2 byte shall indicate in bit 5: + +- a) 0 if 1 + 1 architecture; +- b) 1 if 1:n architecture. + +#### 7.1.1.6 Control of the bridge + +##### 7.1.1.6.1 1 + 1 uni/bidirectional architecture + +In 1 + 1 architecture, the working channel 1 is permanently bridged to the working and protection section and thus no bridge control is needed. + +##### 7.1.1.6.2 1:n unidirectional architecture + +In 1:n unidirectional architecture, the signal number indicated on the received K1 byte is bridged to the protection section. If extra traffic is supported and if the received K1 byte indicates 0 or 15 and the received K1 byte indicates no Lockout of protection request, the extra traffic signal is bridged to the protection section. + +If, at the bridge end, the protection section is in SF condition, the bridge is frozen (current bridge maintained). + +##### 7.1.1.6.3 1:n bidirectional architecture + +In an 1:n bidirectional architecture, the control of the bridge is done by comparing the signal numbers of the received and sent K1 bytes: + +- a) If the signal number in the received and sent K1 byte indicate the same working traffic signal, the corresponding working traffic signal is bridged to the protection section. +- b) If extra traffic is supported and if the signal number in the received K1 byte indicates 0 or 15, and the sent K1 byte also indicates 0 or 15 (all 4 combinations are allowed), and neither the received nor the transmitted K1 byte indicate a Lockout of protection request, the extra traffic signal is bridged to the protection section. +- c) If neither a) nor b) are fulfilled or the protection section is in SF condition, the bridge is released (null signal bridged) + +#### 7.1.1.7 Control of the selector + +##### 7.1.1.7.1 1 + 1 unidirectional architecture + +In 1 + 1 architecture in unidirectional operation, the selector is controlled by the highest priority local request. If the protection section is in SF condition, the selector is released. + +##### 7.1.1.7.2 1 + 1 bidirectional architecture + +In 1 + 1 architecture in bidirectional operation, the selector is controlled by comparing the signal numbers indicated on received K2 and sent K1 bytes. If there is a match, then the indicated signal is selected from the protection section. If there is a mismatch, the selector is released. Note that a match on 0000 also releases the selector. If the mismatch persists for 50 ms, a mismatch is indicated at reference point MSP\_MP. If the protection section is in SF condition, the selector is released and the mismatch indication is disabled. + +##### 7.1.1.7.3 1:n uni/bidirectional architecture + +In a 1:n architecture, the control of the selector is done by comparing the signal numbers of the received K2 byte and the sent K1 byte: + +- a) If the signal number in the received K2 byte and the sent K1 byte indicate the same working traffic signal, the corresponding working traffic signal is selected from the protection section. +- b) If the signal number in the received K2 byte indicates 15 and the sent K1 byte indicates 0 or 15, the extra traffic signal is selected from the protection section. +- c) If neither a) nor b) are fulfilled, the selector is released (no signal selected). If this condition is present for 50 ms, a K1/K2 mismatch is reported at the reference point MSP\_MP. +- d) If the protection section is in SF condition, the selector is released (no signal selected) and an active K1/K2 mismatch indication is cleared. + +NOTE – In the G.783 definition of the 1:n protocol, the extra traffic was removed from the protection section in case of SD for the protection section. In case of interworking between equipment where the 1:n protocol with extra traffic is designed according to the G.783 definition and between equipment where the protocol is designed according to the new definition of this Recommendation, the equipment with the G.783 definition will report a K1/K2 mismatch failure in case of SD for the protection section. Such a failure shall be ignored by the management. + +#### 7.1.1.8 Transmission and acceptance of APS bytes + +Byte K1 and bits 1 to 5 of byte K2 shall be transmitted on the protection section. Although they may also be transmitted identically on working sections, receivers should not assume so, and should have the capability to ignore this information on the working sections. + +APS bytes shall be accepted as valid only when identical bytes are received in three consecutive frames. + +The following conditions are reported as APS defect conditions at the MSP\_MP and result in the release of the selector in addition to the condition defined in 7.1.1.7. + +- A mismatch of bit 5 of the sent and received K2 for 50 ms (optional); +- In bidirectional operation, an inappropriate code that persists for 50 ms in the received K1 bits 1-4. Appropriate codes are a higher priority request than the local request, an identical request to the local request, or a reverse request for any local request except no request. Any other value that persists for 50 ms is considered an inappropriate code; + +- In bidirectional operation, an inappropriate or invalid traffic signal number that persists for 50 ms in the received K1 bits 5-8. + +### 7.1.2 MSP commands + +The MSP function receives MSP control parameters and switch requests from the synchronous equipment management function at the MSP\_MP reference point. A switch command issues an appropriate external request at the MSP function. Only one switch request can be issued at the MSP\_MP. A control command sets or modifies MSP parameters or requests the MSP status. + +Any external switch command not acknowledged by the far end within 2.5 s should be reported as failed, and the command and K-byte request should be withdrawn. If an external switch command was acknowledged initially but is overruled later on, the external command is dropped consequently. + +NOTE – This behaviour was not fully defined in previous versions of Recommendation G.841 and G.783. + +#### 7.1.2.1 Switch commands + +A switch command issued at the MSP APS controller interface initiates one external bridge request for evaluation as described in 7.1.1.1.1. Switch commands are listed below in the descending order of priority and the functionality of each is described. + +- 1) *Clear* – This command clears all the externally initiated switch commands listed below and WTR at the node to which the command was addressed. + +NOTE – In the G.783 definition of the linear MSP, the clear command did not clear WTR. Equipment which was designed according to the G.783 definition will not clear WTR if a clear command is sent to this equipment. However, it is possible to achieve a similar behavior by a carefully selected sequence of external commands (e.g. manual switch followed by clear). + +- 2) *Lockout of protection* – Denies all normal traffic signals (and the extra traffic signal, if applicable) access to the protection section by issuing a "Lockout of Protection" request unless equal protection switch command is in effect. + +- 3) *Forced switch #* – For normal traffic signal #s, switches normal traffic signal # to the protection section, unless an equal or higher priority switch command is in effect or SF condition exists on the protection section, by issuing a forced switch request for that traffic signal. + +For 1 + 1 systems or 1:n systems without extra traffic, forced switch null traffic signal transfers the normal traffic signal from protection section to the working section, unless an equal or higher priority request is in effect. Since forced switch has higher priority than SF or SD on a working section, this command will be carried out regardless of the condition of the working section(s). "Forced Switch Null Traffic signal" has higher priority than "Forced Switch – Normal Traffic signal #" when both commands are detected at the same time. + +For 1:n systems with extra traffic, forced switch extra traffic signal will transfer the normal traffic signal from the protection section to the working section and restore the extra traffic signal on the protection section, unless an equal or higher priority request is in effect. + +- 4) *Manual switch #* – Switches normal traffic signal # to the protection section, unless a failure condition exists on other sections (including the protection section) or an equal or higher priority switch command is in effect, by issuing a manual switch request for that normal traffic signal. + +For 1 + 1 systems or 1:n systems without extra traffic, manual switch null signal transfers the working section back from protection to the working section, unless an equal or higher priority request is in effect. Since manual switch has lower priority than SF or SD on a working section, this command will be carried out only if the working section is not in SF or + +SD condition. "Manual Switch Null Signal" has higher priority than "Manual Switch – Normal Traffic Signal 1" when both commands are detected at the same time. + +- 5) *Exercise #* – Issues an exercise request for that signal and checks responses on APS bytes, unless the protection section is in use. The switch is not actually completed, i.e. the selector is released by an exercise request on either the sent or the received and acknowledged K1 byte. The exercise functionality may not exist in all MSP functions. + +Note that a functionality and a suitable command for freezing the current status of the MSP function is for further study. + +#### 7.1.2.2 Control commands + +Control commands set and modify MSP protocol operation. The control commands that are currently defined apply only to 1:n (unidirectional or bidirectional) switching. + +Clear Lockout of Normal Traffic Signal from Protection – Clears the Lockout of Normal Traffic Signal from Protection command for the normal traffic signal (or normal traffic signals) specified. + +Lockout of Normal Traffic Signal from Protection – Prevents the specified normal traffic signal (or normal traffic signals) from switching to the protection section. + +These commands are not to be confused with the Lockout of protection request, which prevents all normal or extra traffic signals from using the protection section. The request to lock out an individual normal traffic signal from protection or to clear the lockout of a normal traffic signal from protection shall be received at reference point MSP\_MP. Lockout of Normal Traffic signal from Protection can be activated or cleared for each normal traffic signal independently, and any number of normal traffic signals can be locked out at the same time. The locked-out status of a normal traffic signal is not directly reflected in the K-bytes. + +The operation of lockout of a normal traffic signal from protection depends on the mode of operation at the MS protection sublayer at which it is applied. If the operation is bidirectional, then the lockout also operates bidirectionally. If a section has a lockout of normal traffic signal from protection command applied, then local bridge requests are not issued for the locked-out normal traffic signal (i.e. local conditions for the associated working section and external requests for the normal traffic signal are not considered in the K1 byte generation process), and remote bridge requests for the signal are not acknowledged (i.e. remote requests for the signal are not considered in the K1 byte generation process and the requested bridge is not performed). Note that for bidirectional operation, the lockout of normal traffic signal from protection command must be applied at both ends for proper operation. + +If the operation is unidirectional, the lockout also operates unidirectionally. If a normal traffic signal has a lockout of normal traffic signal from protection command applied, then local bridge requests are not issued for the locked out normal traffic signal. However, remote bridge requests for that normal traffic signal are acknowledged by performing the bridge and signalling that bridge in the K2 byte. + +### 7.1.3 MSP conditions + +The following MSP conditions can trigger protection switching: + +SF is defined as the presence of the TSFprot condition generated by the MS Trail Termination function defined in Recommendation G.783. + +NOTE – The SF condition is extended for the protection section. See 7.1.1.8. + +Signal Degrade is defined as the presence of the TSD condition generated by the MS Trail Termination function defined in Recommendation G.783. + +### 7.1.4 Switch operation + +#### 7.1.4.1 1:n bidirectional switching without extra traffic + +Table 7-4 illustrates protection switching action between two multiplexer sites, denoted by A and C, of a 1:n bidirectional protection switching system without extra traffic. + +When the protection section is not in use, null signal is indicated on both sent K1 and K2 bytes. Generation of the null signal is equipment dependent. The null signal could be, for example, unequipped, AIS, or an arbitrary normal traffic signal bridged to the protection section at the head-end. The tail-end must not assume or require any specific signal on the protection section. For example, in the example in Table 7-4, site C may bridge normal traffic signal 3 as the null signal, while site A may bridge normal traffic signal 4 as the null signal. + +When a fail condition is detected or a switch command is received at the tail end of a multiplex section, the protection logic compares the priority of this new condition with the request priority of the traffic signal on the protection section. The comparison includes the priority of any bridge order; i.e. of a request on received K1 byte. If the new request is of higher priority, then the K1 byte is loaded with the request and the number of the traffic signal requesting use of the protection section. In the example, SD is detected at C on working section 2, and this condition is sent on byte K1 as a bridge order at A. + +At the head-end, when this new incoming K1 byte has been verified (after being received identically for three successive frames) and evaluated (by the priority logic), the requested normal traffic signal is bridged onto the protection section, outgoing byte K2[1-4] is sent to confirm the requested bridge, and outgoing byte K1 is set with a reverse request to order a bridge at the tail-end for that normal traffic signal, initiating a bidirectional switch. Note that a reverse request is returned for exerciser and all other requests of higher priority. This clearly identifies which end originated the switch request. If the head-end had also originated an identical request (not yet confirmed by a reverse request) for the same signal, then both ends would continue transmitting the identical K1 byte and perform the requested switch action. + +Also, at the head-end, the indicated traffic signal is bridged to protection. When the signal is bridged, byte K2 is set to indicate the number of the traffic signal on protection. + +At the tail-end, when the traffic signal on received byte K2 matches the number of the traffic signal requesting the switch, that traffic signal is selected from protection. This completes the switch of a traffic signal to protection for one direction. The tail-end also performs the bridge as ordered by byte K1 and indicates the bridged signal on byte K2. + +The head-end completes the bidirectional switch by selecting the signal from protection when it receives a matching K2 byte. + +If the switch is not completed because the requested/bridged signals did not match within 50 ms, the selectors would remain released and the failure of the protocol would be indicated. This may occur when one end is provisioned as unidirectional and the other as bidirectional. A mismatch may also occur when a locked-out traffic signal at one end is not locked out at the other. Note that a mismatch may also occur when a 1 + 1 architecture connects to a 1:1 architecture (which is not in a provisioned for 1 + 1 state), due to a mismatch of bit 5 on K2 bytes. This may be used to provision the 1:1 architecture to operate as 1 + 1. + +The example further illustrates a priority switch, when an SF condition on working section 1 pre-empts the normal traffic signal 2 switch. Note that selectors are temporarily released before selecting normal traffic signal 1 from protection due to temporary signal number mismatch on sent K1 and received K2 bytes. Further in the example, switching normal traffic signal 2 back to protection after failed section 1 is repaired is illustrated. + +When the switch is no longer required, e.g. the failed working section has recovered from failure and wait-to-restore has expired, the tail-end indicates No Request for null signal on byte K1 (0000 0000). This releases the selector due to section number mismatch. + +The head end then releases the bridge and replies with the same indication on byte K1 and null signal indication on byte K2. The selector at the head-end is also released due to mismatch. + +Receiving null signal on K1 byte causes the tail-end to release the bridge. Since the K2 bytes now indicate null signal which matches the null signal on the K1 bytes, the selectors remain released without any mismatch indicated, and restoration is completed. + +**Table 7-4/G.841 – 1:n bidirectional protection switching without extra traffic example** + +| Failure condition
or controller
state | APS bytes | | | | Action | | +|-----------------------------------------------------|-----------|-----------|-----------|-----------|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| | C → A | | A → C | | | | +| | Byte K1 | Byte K2 | Byte K1 | Byte K2 | At C | At A | +| No failures
(protection
section not in use) | 0000 0000 | 0000 1000 | 0000 0000 | 0000 1000 | Null signal is
bridged to
protection.
Selector is
released. | Null signal is
bridged to
protection.
Selector is
released. | +| Working section 2
degraded in
direction A → C | 1010 0010 | 0000 1000 | 0000 0000 | 0000 1000 | Failure detected.
Request normal
traffic signal 2
bridge – SD. | | +| | 1010 0010 | 0000 1000 | 0010 0010 | 0010 1000 | | Bridge normal
traffic signal 2.
Reverse request
normal traffic
signal 2 bridge. | +| | 1010 0010 | 0010 1000 | 0010 0010 | 0010 1000 | Switch normal
traffic signal 2
from protection
section. Bridge
normal traffic
signal 2 to
protection. | | +| | 1010 0010 | 0010 1000 | 0010 0010 | 0010 1000 | | Switch normal
traffic signal 2
from protection.
Bidirectional
switch completed. | +| Working section 1
failed in direction
C → A | 1010 0010 | 0010 1000 | 1100 0001 | 0000 1000 | | Failure detected.
Request normal
traffic signal 1
bridge – SF.
Release normal
traffic signal 2
switch. | + +**Table 7-4/G.841 – 1:n bidirectional protection switching without extra traffic example (continued)** + +| Failure condition
or controller
state | APS bytes | | | | Action | | +|-----------------------------------------------------------|-----------|-----------|-----------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| | C → A | | A → C | | | | +| | Byte K1 | Byte K2 | Byte K1 | Byte K2 | At C | At A | +| (This pre-empts
the normal traffic
signal 2 switch) | 0010 0001 | 0001 1000 | 1100 0001 | 0010 1000 | Bridge normal
traffic signal 1 to
protection. Reverse
request normal
traffic signal 1
bridge.
Release normal
traffic signal 2
switch. | | +| | 0010 0001 | 0001 1000 | 1100 0001 | 0001 1000 | | Switch normal
traffic signal 1.
Bridge normal
traffic signal 1. | +| | 0010 0001 | 0001 1000 | 1100 0001 | 0001 1000 | Switch normal
traffic signal 1.
Bidirectional
switch completed. | | +| Working section 1 | 0010 0001 | 0001 1000 | 0110 0001 | 0001 1000 | | Wait to restore. | +| Repaired
(Working
section 2 still
degraded) | 1010 0010 | 0001 1000 | 0110 0001 | 0001 1000 | Request normal
traffic signal 2
bridge.
Release normal
traffic signal 1
switch. | | +| | 1010 0010 | 0001 1000 | 0010 0010 | 0010 1000 | | Bridge normal
traffic signal 2.
Reverse request
normal traffic
signal 2 bridge.
Release normal
traffic signal 1
switch. | +| | 1010 0010 | 0010 1000 | 0010 0010 | 0010 1000 | Bridge normal
traffic signal 2.
Switch normal
traffic signal 2. | | +| | 1010 0010 | 0010 1000 | 0010 0010 | 0010 1000 | | Switch normal
traffic signal 2.
Bidirectional
switch completed. | +| Working section 2
repaired | 0110 0010 | 0010 1000 | 0010 0010 | 0010 1000 | Wait to restore
normal traffic
signal 2. | | + +**Table 7-4/G.841 – 1:n bidirectional protection switching without extra traffic example (concluded)** + +| Failure condition
or controller
state | APS bytes | | | | Action | | +|---------------------------------------------|-----------|-----------|-----------|-----------|------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| | C → A | | A → C | | | | +| | Byte K1 | Byte K2 | Byte K1 | Byte K2 | At C | At A | +| Wait to restore
expired
(no failures) | 0000 0000 | 0010 1000 | 0010 0010 | 0010 1000 | Drop normal traffic
signal 2 bridge
order. Release
normal traffic
signal 2 switch. | | +| | 0000 0000 | 0010 1000 | 0000 0000 | 0000 1000 | | Drop normal traffic
signal 2 bridge.
Drop normal traffic
signal 2 bridge
request.
Release normal
traffic signal 2
switch. | +| | 0000 0000 | 0000 1000 | 0000 0000 | 0000 1000 | Drop normal traffic
signal 2 bridge.
Null signal is
bridged to
protection. | Null signal is
bridged to
protection. | + +#### 7.1.4.2 1:1 bidirectional switching with extra traffic + +Table 7-5 illustrates protection switching action between two multiplexer sites, denoted by A and C, of a 1:n bidirectional protection switching system with extra traffic. + +When the protection section is not in use, the extra traffic signal is transferred via the protection section. + +When a signal fail or signal degrade condition is detected or a switch command is received at the tail end of a multiplex section, the protection logic compares the priority of this new condition with the request priority of the signal (if any) on the protection. The comparison includes the priority of any bridge order; i.e. of a request on received K1 byte. If the new request is of higher priority, then the K1 byte is loaded with the request and the number of the signal requesting use of the protection section. In the example, SD is detected at C on working section 2, and this condition is sent on byte K1 as a bridge order at A. + +At the head-end, when this new K1 byte has been verified and evaluated (by the priority logic), byte K1 is set with a reverse request as a confirmation of the signal to use the protection and order a bridge at the tail-end for that signal. This initiates a bidirectional switch. Note that a reverse request is returned for exerciser and all other requests of higher priority. This clearly identifies which end originated the switch request. If the head-end had also originated an identical request (not yet confirmed by a reverse request) for the same channel, then both ends would continue transmitting the identical K1 byte and perform the requested switch action. + +Also, at the head-end, the indicated signal is bridged to protection. When the signal is bridged, byte K2 is set to indicate the number of the signal on protection. + +At the tail-end, when the signal number on received byte K2 matches the number of the signal requesting the switch, that signal is selected from protection. This completes the switch to protection + +for one direction. The tail-end also performs the bridge as ordered by byte K1 and indicates the bridged signal on byte K2. + +The head-end completes the bidirectional switch by selecting the signal from protection when it receives a matching K2 byte. + +If the switch is not completed because the requested/bridged signal did not match within 50 ms, the selectors would remain released and the failure of the protocol would be indicated. This may occur when one end is provisioned as unidirectional and the other as bidirectional. A mismatch may also occur when a locked-out signal at one end is not locked out at the other. Note that a mismatch may also occur when a 1 + 1 architecture connects to a 1:1 architecture (which is not in a provisioned for 1 + 1 state), due to a mismatch of bit 5 on K2 bytes. This may be used to provision the 1:1 architecture to operate as 1 + 1. + +The example further illustrates a priority switch, when an SF condition on working section 1 pre-empts the WS 2 switch. Note that selectors are temporarily released before selecting WS 1, due to temporary signal number mismatch on sent K1 and received K2 bytes. Further in the example, switching back WS 2 after failed section 1 is repaired is illustrated. + +When the switch is no longer required, e.g. the failed working section has recovered from failure and wait-to-restore has expired, the tail end indicates No Request for extra traffic signal on byte K1 (null signal if extra traffic is not provided). This releases the selector and bridge due to signal number mismatch. The head-end then releases the selector, bridges the extra traffic signal and replies with the same indication on byte K1 and extra traffic signal indication on byte K2. The tail-end now selects and bridges the extra traffic signal and replies with extra traffic signal indication on byte K2. The head end selects the extra traffic in response, which completes the bidirectional switch to the extra traffic signal. + +**Table 7-5/G.841 – 1:n bidirectional protection switching with extra traffic example** + +| Failure condition
or controller
state | APS bytes | | | | Action | | +|---------------------------------------------------|-----------|-----------|-----------|-----------|--------------------------------------------------------------------------------------|-----------------------------------------------------------------| +| | C → A | | A → C | | | | +| | Byte K1 | Byte K2 | Byte K1 | Byte K2 | At C | At A | +| No failures (extra traffic on protection section) | 0000 1111 | 1111 1000 | 0000 1111 | 1111 1000 | Extra traffic signal is bridged and selected. | Extra traffic signal is bridged and selected. | +| Working section 2 degraded in direction A → C | 1010 0010 | 0000 1000 | 0000 1111 | 1111 1000 | Failure detected.
Order WS 2 bridge – SD.
Release bridge.
Release selector. | | +| | 1010 0010 | 0000 1000 | 0010 0010 | 0010 1000 | | Release selector.
Reverse order WS 2 bridge.
Bridge WS 2. | +| | 1010 0010 | 0010 1000 | 0010 0010 | 0010 1000 | Select WS 2.
Bridge WS 2. | | +| | 1010 0010 | 0010 1000 | 0010 0010 | 0010 1000 | | Select WS 2.
Bidirectional switch completed. | + +**Table 7-5/G.841 – 1:n bidirectional protection switching with extra traffic example (concluded)** + +| Failure condition
or controller
state | APS bytes | | | | Action | | +|---------------------------------------------------------------|-----------|-----------|-----------|-----------|--------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| | C → A | | A → C | | | | +| | Byte K1 | Byte K2 | Byte K1 | Byte K2 | At C | At A | +| Working section 1 failed in direction C → A | 1010 0010 | 0010 1000 | 1100 0001 | 0000 1000 | | Failure detected
Order WS 1 bridge – SF.
Release selector.
Release bridge. | +| (This pre-empts the WS 2 switch) | 0010 0001 | 0001 1000 | 1100 0001 | 0000 1000 | Release WS 2 selector.
Reverse order WS 1 bridge.
Bridge WS 1. | | +| | 0010 0001 | 0001 1000 | 1100 0001 | 0001 1000 | | Select WS 1.
Bridge WS 1. | +| | 0010 0001 | 0001 1000 | 1100 0001 | 0001 1000 | Select WS 1.
Bidirectional switch completed. | | +| Working section 1 repaired | 0010 0001 | 0001 1000 | 0110 0001 | 0001 1000 | | Wait to restore. | +| (Working section 2 still degraded) | 1010 0010 | 0000 1000 | 0110 0001 | 0001 1000 | Order WS 2 bridge.
Release selector.
Release bridge. | | +| | 1010 0010 | 0000 1000 | 0010 0010 | 0010 1000 | | Reverse order WS 2 bridge.
Bridge WS 2.
Release selector. | +| | 1010 0010 | 0010 1000 | 0010 0010 | 0010 1000 | Bridge WS 2.
Select WS 2. | | +| | 1010 0010 | 0010 1000 | 0010 0010 | 0010 1000 | | Select WS 2.
Bidirectional switch completed. | +| Working section 2 repaired | 0110 0010 | 0010 1000 | 0010 0010 | 0010 1000 | Wait to restore WS 2. | | +| Wait to restore expired (no failures, extra traffic selected) | 0000 1111 | 0000 1000 | 0010 0010 | 0010 1000 | Order extra traffic bridge – NR.
Release selector.
Release bridge. | | +| | 0000 1111 | 0000 1000 | 0000 1111 | 1111 1000 | | Order extra traffic bridge – NR.
Bridge extra traffic.
Release selector. | +| | 0000 1111 | 1111 1000 | 0000 1111 | 1111 1000 | Bridge extra traffic.
Select extra traffic. | | +| | 0000 1111 | 1111 1000 | 0000 1111 | 1111 1000 | | Select extra traffic.
Bidirectional switch completed. | + +#### **7.1.4.3 1:n unidirectional switching** + +All actions are as described in 7.1.4.1 except that the unidirectional switch is completed when the tail-end selects from protection the section for which it issued a request. This difference in operation is obtained by not considering remote requests in the priority logic and therefore not issuing reverse requests. + +#### **7.1.4.4 1 + 1 unidirectional switching** + +For 1 + 1 unidirectional switching, the signal selection is based on the local conditions and requests. Therefore each end operates independently of the other end, and bytes K1 and K2 are not needed to coordinate switch action. However, byte K1 is still used to inform the other end of the local action, and bit 5 of byte K2 is set to zero. + +#### **7.1.4.5 1 + 1 bidirectional switching** + +The operation of 1 + 1 bidirectional switching can be optimized for a network in which 1:n protection switching is widely used and which is therefore based on compatibility with a 1:n arrangement; alternatively it can be optimized for a network in which predominantly 1 + 1 bidirectional switching is used. This leads to two possible switching operations described below and in Annex B. + +##### **7.1.4.5.1 1 + 1 bidirectional switching compatible with 1:n bidirectional switching** + +Bytes K1 and K2 are exchanged as described in 7.1.4.1 to complete a switch. Since the bridge is permanent, i.e. the normal traffic signal is always bridged to the protection section, normal traffic signal 1 is indicated on byte K2, unless received K1 indicates null signal (0). Switching is completed when both ends select the signal from protection, and may take less time because K2 indication does not depend on a bridging action. + +For revertive switching, the restoration takes place as described in 7.1.4.1. For non-revertive switching, Table 7-6 illustrates the operation of a 1 + 1 bidirectional protection switching system. + +For non-revertive operation, assuming the normal traffic signal is on protection, when the working section is repaired, or a switch command is released, the tail-end maintains the selection and indicates do not revert for the normal traffic signal. The head-end also maintains the selection and continues indicating reverse request. The do not revert is removed when pre-empted by a failure condition or an external request. + +**Table 7-6/G.841 – Example of 1 + 1 bidirectional switching compatible with 1:n bidirectional switching** + +| Failure condition or controller state | APS bytes | | | | Action | | +|-------------------------------------------------------------|-----------|-----------|-----------|-----------|-------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| | C → A | | A → C | | | | +| | Byte K1 | Byte K2 | Byte K1 | Byte K2 | At C | At A | +| No failures (assume protection section not in use) | 0000 0000 | 0000 0000 | 0000 0000 | 0000 0000 | Selector is released. | Selector is released. | +| Working section 1 failed in direction A → C | 1101 0001 | 0000 0000 | 0000 0000 | 0000 0000 | Failure detected. Request normal traffic signal 1 bridge – SF. | | +| | 1101 0001 | 0000 0000 | 0010 0001 | 0001 0000 | | Indicate normal traffic signal 1 bridged. Reverse request normal traffic signal 1 bridge. | +| | 1101 0001 | 0001 0000 | 0010 0001 | 0001 0000 | Indicate normal traffic signal 1 bridged. Select normal traffic signal from protection section. | | +| | 1101 0001 | 0001 0000 | 0010 0001 | 0001 0000 | | Select normal traffic signal from protection section. Bidirectional switch completed. | +| Working section 1 repaired. Maintain switch (non-revertive) | 0001 0001 | 0001 0000 | 0010 0001 | 0001 0000 | Send Do not revert. | | +| Protection section degraded in direction A → C | 1011 0000 | 0001 0000 | 0010 0001 | 0001 0000 | Failure detected. Request null signal bridge – SD. Select normal traffic signal from working section. | | +| | 1011 0000 | 0001 0000 | 0010 0000 | 0000 0000 | | Reverse request null signal bridge. Drop normal traffic signal bridge indication. Select normal traffic signal from working section. | +| | 1011 0000 | 0000 0000 | 0010 0000 | 0000 0000 | Drop normal traffic signal bridge indication. | | +| Protection section repaired | 0000 0000 | 0000 0000 | 0010 0000 | 0000 0000 | Send no request. | | +| | 0000 0000 | 0000 0000 | 0000 0000 | 0000 0000 | | Send no request. | + +## **7.2 MS shared protection rings** + +### **7.2.1 Two- and four-fibre MS shared protection rings** + +All MS shared protection rings support ring switching. In addition, four-fibre MS shared protection rings support span switching. + +#### **7.2.1.1 Two-fibre MS shared protection rings** + +Two-fibre MS switched rings require only two fibres for each span of the ring. Each fibre carries both working channels and protection channels. On each fibre, half the channels are defined as working channels and half are defined as protection channels. The normal traffic carried on working channels in one fibre are protected by the protection channels travelling in the opposite direction around the ring (See Figure 7-2.). This permits the bidirectional transport of normal traffic. Only one set of overhead channels is used on each fibre. + +Two-fibre MS shared protection rings support ring switching only. When a ring switch is invoked, the normal traffic is switched from the working channels to the protection channels in the opposite direction. + +If Non-pre-emptible Unprotected Traffic (NUT) is supported, selected channels on the working bandwidth and their corresponding protection channels may be provisioned as non-pre-emptible unprotected channels. The remaining working channels are still protected by the corresponding protection channels. The non-pre-emptible unprotected channels will have no BLSR APS protection. + + + +← Fibre (arrow indicates transmission direction) + +Diagram of a two-fibre MS shared protection ring showing four nodes (A, B, C, D) connected in a mesh. Node A and B are in a shaded top section, while C and D are below. Arrows indicate bidirectional transmission between adjacent nodes. A legend indicates that a left-pointing arrow represents a fibre with transmission direction. + +NOTE – Each fibre carries both working and protection traffic, as shown in the exploded view. + +a) View of entire ring + + + +← Arrow indicates direction of transmission + +Fibre + +T1516780-94 + +Exploded view of the shaded portion of the ring between Node A and Node B. It shows two parallel fibres. The top fibre has a left-pointing arrow and contains three layers: Section overhead, Working, and Protection. The bottom fibre has a right-pointing arrow and also contains three layers: Section overhead, Working, and Protection. A legend below shows a single fibre with these three layers and an arrow indicating the direction of transmission. + +b) Exploded view of the shaded portion of the ring + +**Figure 7-2/G.841 – Two-fibre MS shared protection ring** + +#### 7.2.1.2 Four-fibre MS shared protection rings + +Four-fibre MS shared protection rings require four fibres for each span of the ring. As illustrated in Figure 7-3, working and protection channels are carried over different fibres: two multiplex sections transmitting in opposite directions carry the working channels while two multiplex sections, also transmitting in opposite directions, carry the protection channels. This permits the bidirectional transport of normal traffic. The multiplex section overhead is dedicated to either working or protection channels since working and protection channels are not transported over the same fibres. + +Four-fibre MS shared protection rings support ring switching as a protection switch, as well as span switching, though not concurrently. Multiple span switches can coexist on the ring since only the protection channels along one span are used for each span switch. Certain multiple failures (those that affect only the working channels of a span such as electronic failures and cable cuts severing only the working channels) can be fully protected using span switching. + +If NUT is supported, then on each span, selected channels on the working bandwidth and their corresponding protection channels may be provisioned as non-pre-emptible unprotected channels. The remaining working channels are still protected, for both span and ring switching, by their corresponding protection channels. The effect on a selected non-pre-emptible unprotected channel is as follows: + +- ring switching is disabled on that channel everywhere on the ring (as in the two-fibre case); +- span switching is disabled for that channel on the provisioned span. + +Hence, the NUT channel has no MS SPRING APS protection on the provisioned span; on other spans, the same channel (if not provisioned as NUT) has only span switching available to it. Note that if these channels are provisioned as working channels on other spans, they will have lower survivability than other working channels since ring switching is unavailable to them. + +Support of non-pre-emptible unprotected channel provisioning requires that a NUT table be present at each node on the MS SPRING. Figure 7-4 gives a conceptual representation and example of a NUT table. This table contains information to identify the channels that have been provisioned for NUT, and identifies which type of switching (i.e. span or ring switch) is prohibited by the NUT. Since provision of a working channel for non-pre-emptible unprotected automatically ensures that the corresponding protection channel is also provisioned for non-pre-emptible unprotected, only the working channel ID need to be stored in the table. The corresponding table for two-fibre operation only needs a column for ring switching. + +Four-fibre MS shared protection rings may have the capability of operating similar to a linear ADM chain when not fully connected as a continuous ring (i.e. they can lock out ring switches and use span switches only to protect existing traffic). This configuration may exist because an isolated ring segment has been established before all the other spans have been made fully operational. + + + +Fibre carrying working traffic (arrow indicates transmission direction) + +Fibre carrying protection traffic (arrow indicates transmission direction) + +Diagram (a) showing a four-node ring network (Nodes A, B, C, D). Solid lines represent working traffic and dotted lines represent protection traffic. A shaded region between Node A and Node B is labeled 'See exploded view'. Solid arrow pointing left Dotted arrow pointing left + +a) View of entire ring + + + +Direction of transmission + +Arrow indicates direction of transmission + +Section overhead + +AU groups +(carrying working or protection traffic) + +Fibre + +T1516790-94 + +Diagram (b) showing an exploded view of the four fibres between Node A and Node B. Two fibres are for working traffic and two for protection traffic, with directional arrows. A detailed cross-section of a single fibre shows it is split into 'Section overhead' and 'AU groups'. Solid arrow pointing left + +b) Exploded view of the shaded portion of the ring + +**Figure 7-3/G.841 – Four-fibre MS shared protection ring** + + + +Diagram of a four-fibre MS shared protection ring with four nodes: Node A, Node B, Node C, and Node D. Each node is connected to a central switching element. The text 'Four-fibre MS shared protection ring' is in the center. + +- All spans have NUT for AU-4 #1 +- The span between B and C has NUT on AU-4 #2 + +Node A + +| AU-4 # | Ring switch | Span switch | | +|--------|-------------|-------------|------| +| | | East | West | +| 1 | – | – | – | +| 2 | – | | | +| 3 | | | | +| 4 | | | | +| 5 | | | | +| . | | | | +| . | | | | +| . | | | | + +Node B + +| AU-4 # | Ring switch | Span switch | | +|--------|-------------|-------------|------| +| | | East | West | +| 1 | – | – | – | +| 2 | – | – | | +| 3 | | | | +| 4 | | | | +| 5 | | | | +| . | | | | +| . | | | | +| . | | | | + +Node C + +| AU-4 # | Ring switch | Span switch | | +|--------|-------------|-------------|------| +| | | East | West | +| 1 | – | – | – | +| 2 | – | | – | +| 3 | | | | +| 4 | | | | +| 5 | | | | +| . | | | | +| . | | | | +| . | | | | + +Node D + +| AU-4 # | Ring switch | Span switch | | +|--------|-------------|-------------|------| +| | | East | West | +| 1 | – | – | – | +| 2 | – | | | +| 3 | | | | +| 4 | | | | +| 5 | | | | +| . | | | | +| . | | | | +| . | | | | + +T1529650-98 + +– Indicates that this facility is not available for protection switching. + +NOTE – In this example, "West" refers to the counter-clockwise direction of the ring. + +**Figure 7-4/G.841 – Conceptual representation and example of a NUT table** + +### 7.2.2 Network objectives + +The following network objectives apply: + +- 1) *Switch time* – In a ring with no extra traffic, all nodes in the idle state (no detected failures, no active automatic or external commands, and receiving only Idle K-bytes), and with less than 1200 km of fibre, the switch (ring and span) completion time for a failure on a single span shall be less than 50 ms. On rings under all other conditions, the switch completion time can exceed 50 ms (the specific interval is under study) to allow time to remove extra traffic, or to negotiate and accommodate coexisting APS requests. +- 2) *Transmission delay* – There is no network objective on transmission delay. +- 3) *Hold-off times* – There is no network objective on hold-off times. + +- 4) *Extent of protection* +- For a single point failure, the ring will restore all traffic that would be passing through the failed location had no failure occurred. + - The ring shall restore all traffic possible, even under conditions of multiple bridge requests of the same priority (including the combination of Forced Switch - Ring and Signal Fail - Ring). +- 5) *Switching types* – Bidirectional protection switching shall be provided. +- 6) *APS protocol and algorithm* +- The switching protocol shall be able to accommodate up to 16 nodes on a ring. + - In order to provide an additional degree of protection for the four-fibre ring, a mechanism to perform span switching shall be provided in the APS protocol. + - The APS protocol shall be optimal for the AU-3/4 level of operation. + - The APS protocol and associated OAM&P functions shall accommodate the ability to modify and upgrade the ring. In particular, adding and deleting nodes from the ring shall be accommodated. + - A deterministic process shall be used to avoid misconnecting traffic. + - All spans on a ring shall have equal priority. Therefore, no higher priority spans will exist which would allow ring bridge requests for that span to override (automatically) other span switches of the same type (e.g. Signal Fail, Signal Degrade, or Forced Switch). + - The state of ring (i.e. in the normal or protected state) shall be known at each node. + - A span bridge request shall have higher priority than a ring bridge request of the same type. + - If a ring switch exists and a failure of equal priority occurs on another span requiring a ring switch (including the combination of Forced Switch - Ring and Signal Fail - Ring), then, if the priority of the bridge request is Signal Fail (Ring) or higher, both ring switches shall be established resulting in the ring segmenting into two separate segments. + - AUG squelching shall be done at the switching nodes. +- 7) *Operation modes* +- Revertive switching shall be provided. A switch shall revert only to the working channels and not to a different set of protection channels. + - The ring APS signalling shall provide protection switching for both two-fibre and four-fibre bidirectional MS shared protection rings. +- 8) *Manual control* – The following externally initiated commands shall be supported: Lockout of Protection - Span, Forced Switch - Span, Forced Switch - Ring, Manual Switch - Span, Manual Switch - Ring, Exerciser - Span, and Exerciser - Ring. +- 9) *Switch initiation criteria* – The following automatically initiated commands shall be supported: Signal Failure - Protection, Signal Failure - Span, Signal Failure - Ring, Signal Degrade - Span, Signal Degrade - Ring, Signal Degrade - Protection, Reverse Request - Span, Reverse Request - Ring, Wait-To-Restore, and No Request. + +- 10) *Ring utilization criteria* – Time-slot interchange will allow better utilization of bandwidth of the ring. If Time-Slot Interchange (TSI) is allowed, the traffic having a time-slot interchange through the failed location may or may not be restored. It is for further study whether TSI shall be allowed, and if allowed, whether traffic having time-slot interchange through the failed location will be restored. + +### 7.2.3 Application architecture + +The AU groups that traverse the span between any two adjacent nodes are divided into working channels and protection channels. In the case of the two-fibre ring, the STM-N can be viewed as a multiplex of N AU-4s, where the AU-4s are numbered from 1 to N according to the order that they appear in the multiplex. AU-4s numbered from 1 to N/2 shall be assigned as working channels, and AU-4s numbered from (N/2) + 1 to N shall be assigned as protection channels. Furthermore, the normal traffic carried on working channel *m* is protected by protection channel (N/2) + *m*. For example, an STM-4 can be considered a multiplex of four AU-4s numbered one to four. AU-4s number one and two would be assigned as working channels, and AU-4s number three and four would be assigned as protection channels. This assignment applies to both directions of transmission and to all spans. + +In the case of the four-fibre ring, each working and protection STM-N is carried on a separate fibre. + +The ring APS protocol shall be carried on bytes K1 and K2 in the multiplex section overhead. In the case of the four-fibre ring, the APS protocol is only active on the fibres carrying protection channels. Functions that are required in real time and required to make a protection switch are defined in the ring APS protocol using bytes K1 and K2. Other operations channels, including the regenerator section and multiplex section Data Communications Channels, may also provide protection switching functions that are not time critical (for example, functions that need not be completed within 50 ms). + +Each node on the ring shall be assigned an ID that is a number from 0 to 15, allowing a maximum of 16 nodes on the ring. The ID is independent of the order that the nodes appear on the ring. + +A node on the ring may insert normal or extra traffic into channels in either direction, drop normal or extra traffic from channels from either direction, or pass channels directly through to allow other nodes to be connected. Because MS shared protection rings can support extra traffic, this capability may apply not only to the working channel, but also, as an option, to the protection channels. Each node has a ring map that is maintained by local craft or by an OS and contains information about the assignment of channels that the node handles. An example of such a ring map is provided in Figure 7-5 and an example of a squelch table is provided in Figure 7-6. + +| | Node | +|----|------| +| 1 | A | +| 2 | J | +| 3 | M | +| 4 | P | +| 5 | B | +| 6 | L | +| 7 | K | +| 8 | G | +| 9 | S | +| 10 | E | +| 11 | F | +| 12 | R | +| 13 | C | +| 14 | D | +| 15 | N | +| 16 | H | + + + +Conceptual representation of a ring topology map showing 16 nodes (A through S) connected in a circular fashion. The nodes are arranged clockwise starting from the top-left: A, J, M, P, B, L, K, G, S, E, F, R, C, D, N, H. A label 'T1516800-94' is present at the bottom right of the diagram. + +Figure 7-5/G.841 – Conceptual representation of a ring topology map + + + +| AU number | ← West | | Node | East → | | +|-----------|--------|---|------|--------|---| +| | A | B | C | D | A | +| 1 | ← VC → | | | | | +| 2 | ← VC → | | | | | +| 3 | ← VC → | | | | | +| 4 | ← VC → | | | | | +| 5 | ← VC → | | | | | +| 6 | ← VC → | | | | | + +Sample traffic routing for a four-node ring. + + + +Node A + +| | West | | | East | | | +|---|------|-----|----|------|-----|----| +| | Src | Dst | VC | Src | Dst | VC | +| 1 | | | | A | B | ✓ | +| 2 | | | | A | D | ✓ | +| 3 | A | C | ✓ | A | C | | +| 4 | A | D | | A | B | | +| 5 | A | B | | | | | +| 6 | B | C | | C | B | | + +Node B + +| | West | | | East | | | +|---|------|-----|----|------|-----|----| +| | Src | Dst | VC | Src | Dst | VC | +| 1 | B | A | ✓ | B | D | | +| 2 | D | A | ✓ | A | D | ✓ | +| 3 | C | A | | A | C | | +| 4 | B | A | | B | C | | +| 5 | | | | B | A | | +| 6 | B | C | | B | C | | + +Node C + +| | West | | | East | | | +|---|------|-----|----|------|-----|----| +| | Src | Dst | VC | Src | Dst | VC | +| 1 | D | B | ✓ | B | D | ✓ | +| 2 | D | A | ✓ | A | D | ✓ | +| 3 | C | A | | C | A | ✓ | +| 4 | C | B | | C | D | | +| 5 | A | B | | B | A | | +| 6 | C | B | | C | B | | + +Node D + +| | West | | | East | | | +|---|------|-----|----|------|-----|----| +| | Src | Dst | VC | Src | Dst | VC | +| 1 | D | B | | | | | +| 2 | D | A | ✓ | | | | +| 3 | A | C | ✓ | C | A | ✓ | +| 4 | D | C | | D | A | | +| 5 | A | B | | B | A | | +| 6 | B | C | | C | B | | + +T1516810-94 + +Src Node at which an HO VC enters the ring or is sourced + Dst Node at which an HO VC exists the ring or is terminated + ✓ Indicates an LO VC organized AU + +NOTE – Marking of AUs for LO VC access is optional. All connections in this example are bidirectional. + +**Figure 7-6/G.841 – Conceptual representation of node cross-connect map** + +When no protection switches are active on the ring, each node sources the K-bytes in each direction indicating no bridge request. In general, the protection channels that are sourced at each node contain Path Unequipped, as specified in Recommendation G.707. This point is for further study. The exception is extra traffic that may be added, dropped, or passed through similar to normal traffic. + +A switch shall be initiated by one of the criteria specified in 7.2. A failure of the APS protocol or controller shall not trigger a protection switch. It is assumed, however, that the appropriate alarms will be generated. + +A two-fibre ring only uses ring switches to restore traffic. A four-fibre ring has the additional option of span switching. Specifically, from the perspective of a node in a four-fibre ring, two protection channels exist: a short path over the span used in the span switch, and a long path over the long way around the ring used in a ring switch. With span switching, each span in a four-fibre ring can behave similar to a 1:1 protected linear system. Therefore, failures that only affect the working channels and not the protection channels can be restored using a span switch. Four-fibre rings should use span switching when possible so that multiple span switches can coexist. Therefore, span switching has priority over ring switching for bridge requests of the same type (e.g. Signal Fail, Signal Degrade, Forced Switch). Lower priority span switches shall not be maintained in the event of a higher priority ring bridge request. + +When a node determines that a switch is required, it sources the appropriate bridge request in the K-bytes in both directions, i.e. the short path and long path. + +In the case of unidirectional failures, signalling on the short path may permit faster switch completion. Since the node across the failed span will typically see the short-path bridge request much sooner than the long-path bridge request status (or bridge request), it can initiate its own bridge requests more quickly. In the case of span bridge requests on four-fibre rings, signalling on the long path informs other nodes on the ring that a span switch exists elsewhere on the ring. This mechanism denies lower priority ring switches. + +The destination node is the node that is adjacent to the source node across the failed span. When a node that is not the destination node receives a higher priority bridge request, it enters the appropriate pass-through state. In this way, the switching nodes can maintain direct K-byte communication on the long path. Note that in the case of a bidirectional failure such as a cable cut, the destination node would have detected the failure itself and sourced a bridge request in the opposite direction around the ring. + +When the destination node receives the bridge request, it performs the bridge. If the bridge request is of a ring type, the node bridges the channels that were entering the failed span onto the protection channels in the opposite direction. In addition, for signal fail-ring switches, the node also performs the switch to protection channels. + +For example, consider a section of a ring consisting of four nodes, A, B, C, D where the span between B and C has failed. This situation is illustrated in Figure 7-7. In a two-fibre ring, B will bridge the normal traffic from AU-4 channels numbered 1 to N/2 (working) that were being transmitted from B to C onto AU-4 channels (N/2) + 1 to N (protection) being transmitted from B to A and around the ring ultimately back to C. This action is referred to as a bridge. C will switch the normal traffic from protection channels received from B by way of A back onto the working channels toward D. This action is referred to as the switch. + +If the ring switch in this example is on a four-fibre ring, B will bridge the normal traffic from channels that were being transmitted on the working fibre from B to C onto the channels being transmitted on the protection fibre from B to A. Similarly, C will switch the normal traffic from channels on the protection fibre received from D onto the channels transmitted on the working fibre to D. + +The end result for this example is that all the channels that were being sent from B to C across the failed span are now sent from B to C the long way around the ring through nodes A and D. Symmetrical actions will take place to restore the channels that were being sent from C to B. + +When the failure has cleared, the nodes sourcing those bridge requests will drop their respective requests and switches. Other nodes on the ring will stop passing through the protection channels and the K-bytes. In general, normal traffic only reverts from the protection channels back to the working channels. Specifically, in a four-fibre ring, if a ring switch is active on the long-path protection channels, and the short-path protection channels become available, the service will not be switched to the short-path protection channels unless a new bridge request pre-empts the long-path protection channels. + +Ring and span switches can be pre-empted by bridge requests of higher priority as determined by Table 7-8. For example, consider that a span switch is up due to a signal degrade on that span, and a ring switch is required due to a failure on another span that affects both the working and protection channels. A ring bridge request will be generated, the span switch dropped, and the ring switch established. + +Externally initiated commands that are denied or pre-empted due to a higher priority APS request at that node are not allowed to pend. + +As soon as a request of higher priority than the No Request priority is received by the node, and only if that request is a ring request other than EXER-R, or requires the usage of the protection channels carrying the extra traffic, extra traffic is pre-empted. + +If a ring switch exists and a failure of equal priority occurs on another span requiring a ring switch (including the combination of SF-R and FS-R), then, if the priority of the bridge request is Signal Fail (Ring) or higher, both ring switches shall be established resulting in the ring segmenting into two separate segments. Otherwise, if the priority of the bridge requests is lower than Signal Fail (Ring), the new bridge request shall not be established and the first switch shall be dropped. + +In general, proper operation of the ring relies on all nodes having knowledge of the state of the ring, so that nodes do not pre-empt a bridge request unless they have a higher priority bridge request. In order to accommodate this ring state knowledge, signalling over the long path during a bridge request, in addition to the short path, shall be used. For example, although span bridges can be established with only short-path signalling, a Bridged indication is sent on the long path in order to inform other nodes of the state of the ring. In addition, OAM&P messages transported over the DCC can be used to determine the details regarding the condition of the ring. + + + +The diagram illustrates a two-fibre MS shared protection ring with four nodes: Node A (top-left), Node B (top-right), Node C (bottom-right), and Node D (bottom-left). A box labeled "Additional network nodes and spans" is connected to Node D. A failure, indicated by a large 'X', is shown on the vertical fibre between Node B and Node C. At Node B, a bridge (solid line) and a switch (dotted line) are shown. At Node C, a bridge (solid line) and a switch (dotted line) are also shown. The legend indicates that solid lines represent Bridges and dotted lines represent Switches. The channel legend shows a grey bar for "Working channels, AU-4 number 1 to N/2" and a white bar for "Protection channels, AU-4 number (N/2 + 1) to N". The reference code T1516820-94 is present near Node C. + +Diagram of a two-fibre MS shared protection ring with four nodes (A, B, C, D) and a failure at Node B. It shows working and protection channels, and legends for Bridge, Switch, and channel types. + +**Figure 7-7/G.841 – Bridge and switch in a two-fibre MS shared protection ring** + + + +Diagram (a) showing the normal state before node failure. It depicts a network of six nodes (A, B, C, D, E, F) arranged in a rectangular mesh. Node A is top-left, B is top-middle, C is top-right. F is bottom-left, E is bottom-middle, D is bottom-right. Circuit Q is shown as a double line connecting Node C to an external source. Circuit R is shown as a double line connecting Node F to an external source. Working paths are indicated by thick grey bars on the links between nodes. Specifically, thick grey bars are on the link between A and B, B and C, F and E, and E and D. Thin white bars (protection) are also present on these links. + +a) Normal state before node failure + + + +Diagram (b) showing the misconnection after node failure. Node A is marked with a large 'X', indicating it has failed. Circuit Q remains connected to Node C. Circuit R is now misconnected: its path from Node F goes up to Node A (which is failed), then is rerouted through Node B and Node C to Node D, and finally down to Node F. This creates a loop. The thick grey working bars are now on the link between B and C, C and D, and F and E. Thin white protection bars are on the link between A and B, and F and E. + +T1516830-94 + +b) Misconnection after node failure + +| Circuit | Time-slot assignment | Channel | +|---------|----------------------|---------| +| Q | 1W | Working | +| R | 1W | Working | + + + +Legend for the diagram. It shows three items: a thick grey rectangle labeled 'Working', a thin white rectangle labeled 'Protection', and a double-headed arrow labeled 'Circuit transporting service'. + +NOTE – Under the "Time-slot assignment" column, the designation "1W " indicates that it is the first time slot in the capacity reserved for working traffic. + +**Figure 7-8/G.841 – Example of misconnection** + +#### 7.2.3.1 Extra traffic + +During fault-free conditions, it is possible to use the protection channels to carry additional traffic. This additional traffic, which is referred to as extra traffic, has lower priority than the normal traffic on the working channels and has no means for protection. The extra traffic is set up by provisioning the add and drop nodes for the traffic. Intermediate nodes along the ring are provisioned so that the protection channel AU-3/4s carrying extra traffic are passed through the node (Protection channels that are not carrying extra traffic are terminated at the intermediate nodes). Nodes that are inserting, dropping, or passing through extra traffic indicate its presence on those spans by inserting the extra traffic code in byte K2. Note that non-pre-emptible unprotected traffic is not considered extra traffic, and as such, shall not set the ET code. + +When it becomes necessary to bridge the normal traffic onto the protection channels (due to a failure or an externally initiated command) the extra traffic is pre-empted and dropped on the spans whose protection channels are required for the protection switch. Extra traffic circuits that have their source removed by this preemption shall be squelched with AU-AIS. When the affected nodes return to the idle state, the extra traffic is restored. + +#### 7.2.3.2 Squelching to avoid misconnected traffic + +In order to perform a ring switch, the protection channels are essentially shared among each span of the ring. Also, extra traffic may reside in the protection channels when the protection channels are not currently being used to restore normal traffic transported on the working channels. Thus, each protection channel time slot is subject to use by multiple services (services from the same time slot but on different spans, and service from extra traffic). With no extra traffic on the ring, under certain multiple point failures, such as those that cause node(s) isolation, services (from the same time slot but on different spans) may contend for access to the same protection channel time slot. This yields a potential for misconnected traffic. With extra traffic on the ring, even under single point failures, normal traffic on the working channels may contend for access to the same protection channel time slot that carries the extra traffic. This also yields a potential for misconnected traffic. + +Without a mechanism to prevent misconnection, the following failure scenario would yield misconnections. Referring to Figure 7-8, a cut in both the spans between nodes A and F and between nodes A and B (isolating node A) causes circuits Q and R to attempt to access time slot #1P on the protection channels. + +A potential misconnection is determined by identifying the nodes that will act as the switching nodes for a bridge request, and by examining the traffic that will be affected by the switch. The switching nodes can be determined from the node addresses in the K1 and K2 bytes. The switching nodes determine the traffic affected by the protection switch from the information contained in their ring maps and from the identifications of the switching nodes. Potential misconnections shall be squelched by inserting the appropriate AU-AIS in those time slots where misconnected traffic could occur. Specifically, the traffic that is sourced or dropped at the node(s) isolated from the ring by the failure shall be squelched. For rings operating at an AU-4 level, this squelching occurs at the switching nodes. AU level squelching occurs for the normal or extra traffic into or out of the protection channels (i.e. normal traffic into or out of working channels is never squelched). For rings using lower order VC access, squelching locations are under study. + +For example, consider a segment of a ring consisting of three nodes, A, B, and C where B has failed. In a typical scenario, both A and C will send bridge requests destined for B. When A sees the bridge request from C, and sees that B is between A and C (from the node map) it can deduce that B is isolated from the ring. A and C will use their respective maps to find out which channels are added or dropped by B. A and C will squelch these channels before the ring switch is performed by + +inserting AU-AIS. Thus, any node on the ring that was connected to B will now receive AIS on those channels. + +Each of the ring maps, then, shall contain at minimum: + +- 1) a ring map that contains information regarding the order in which the nodes appear on the ring; +- 2) a cross-connect map that contains the AU-4 time-slot assignments for traffic that is both terminated at that node and passed-through that node; +- 3) a squelch table that contains, for each of these AU-4 time slots, the node addresses at which the traffic enters and exits the ring; and +- 4) an optional indication of whether the AU is being accessed at the lower order VC level somewhere on the ring. + +An example of such ring maps is given in Figures 7-3 and 7-4. For lower order VC access, the map requirements are under study. + +An MS SPRING may, as an option, support unidirectional traffic. Unidirectional traffic may be one of the following: + +- a simple directed connection sourced in one node and terminated in another node; +- a multiply dropped circuit (such as the drop and continue used in ring interworking [see Recommendation G.842]); +- a multiply sourced circuit (such as the reverse direction of the drop and continue direction of a ring interworking circuit). + +In the event of a node failure, the squelching performed for these circuits is based only on the following: + +- (for a simple directed connection) the failure of the source node or the failure of the destination node; +- (for a multiply dropped circuit) the failure of the source node or the failure of the last drop node; +- (for a multiply sourced circuit) the failure of the first source node or the failure of the destination node. + +In order to prevent misconnection of extra traffic, the bridge or switch operations are not executed until the switching nodes see that the extra traffic code is removed from the spans required for the protection switch. + +A node that pre-empts extra traffic should squelch the extra traffic channels that are pre-empted in the following manner: + +- for a node executing a span switch that pre-empts extra traffic on that span, extra traffic is squelched by inserting AU-AIS on extra traffic channels from that span that are dropped at that node (i.e. on the low-speed side), and inserting AU-AIS on extra traffic channels from that span that pass through the node (i.e. on the high-speed side), as long as those protection channels are not required for a protection switch. +- for a node executing a ring switch, extra traffic is squelched by inserting AU-AIS on extra traffic channels that are dropped at that node (i.e. on the low-speed side). +- for a node entering full pass-through, extra traffic is squelched by inserting AU-AIS on extra traffic channels that are dropped at that node (i.e. on the low-speed side). + +#### 7.2.3.3 LO VC access + +Some nodes on the ring, referred to as LO VC access nodes, may be capable of inserting, dropping, or cross-connecting LO VCs from the AUs. When multiple nodes on the ring add LO VCs or crossconnect LO VCs between AUs, the payload for a given AU may have multiple source nodes or be dropped among multiple nodes. Such AUs are referred to in this Recommendation as LO VC-accessed AUs. LO VC access is for further study. + +### 7.2.4 Switch initiation criteria + +The requests to perform protection switching can be initiated either externally or automatically. Externally initiated commands are entered by way of the Operations System (OS) or the craftsperson interface. Subclause 7.2.4.1 describes these externally initiated commands available at the OS, craftsperson, or both interfaces. Automatically initiated commands can also be initiated based on multiplex section and equipment performance criteria, received bridge requests, and received bridge request status information. Subclause 7.2.4.2 provides the automatically initiated command criteria. + +The bridge requests related to span switching (except for Lockout of Protection) are used only for four-fibre MS shared protection rings. + +The No Request (NR) code is transmitted when there is no need to use the protection channels. + +#### 7.2.4.1 Externally initiated commands + +Externally initiated commands are initiated at an NE by either the OS or the craftsperson. The externally initiated command may be transmitted to the appropriate NE via the APS bytes, the TMN, or over the local craft interface. The bridge requests are evaluated by the priority algorithm in the protection switching controller. + +##### 7.2.4.1.1 Commands not signalled on the APS channel + +The descriptions of the externally initiated commands are provided below. + +**clear:** This command clears the externally initiated command and WTR at the node to which the command was addressed. The NE-to-NE signalling following removal of the externally initiated commands is performed using the NR code. + +The following two commands are useful if one span has excessive switching to protection. Another use for these commands includes blocking protection access for some spans that have only traffic that does not need protection. The commands are not time critical (i.e. not needed to be completed in tens of milliseconds). Thus, they can be transmitted over the DCC. + +**lockout of working channels - ring switch:** This command prevents the normal traffic from working channels over the addressed span from accessing the protection channels for a ring switch by disabling the node's capability to request a ring protection switch of any kind. If any normal traffic is already on protection, the ring bridge is dropped regardless of the condition of the working channels. If no other bridge requests are active on the ring, the NR code is transmitted. This command has no impact on the use of protection channels for any other span. For example, the node can go into any of the pass-through modes. + +**lockout of working channels - span switch:** This command prevents the normal traffic from the working channels over the addressed span from accessing the protection channels for a span switch. If any normal traffic is already on protection, the span switch is dropped regardless of the condition of the working channels. If no other bridge requests are active on the ring, the NR code is transmitted. This command has no impact on the use of protection channels for any other span. + +**lockout of protection - all spans:** This command prevents protection switching on the entire ring. If any normal traffic is using the protection facility on any span, this command causes normal traffic to switch back to the working channels regardless of the condition of the working channels. Note that the K1 and K2 bytes do not support this command. Thus, the command has to be sent to each of the NEs and the Lockout of Protection - Span request is used by each NE to coordinate activities with the far end. + +##### 7.2.4.1.2 Commands using the APS bytes + +The following commands are carried over the APS bytes. + +**Lockout of Protection - Span (LP-S):** This command prevents the usage of the span for any protection activity and prevents using ring switches anywhere in the ring. If any ring switches exist in the ring, this command causes the switches to drop. If there is a span switch for this span, it is dropped. Thus, all ring switching is prevented (and pre-empted), and span switching is prevented only on the locked-out span. + +**Forced Switch to protection - Ring (FS-R):** This command performs the ring switch of normal traffic from working channels to the protection channels for the span between the node at which the command is initiated and the adjacent node to which the command is destined. This switch occurs regardless of the state of the protection channels, unless the protection channels are satisfying a higher priority bridge request. + +**Forced Switch to protection - Span (FS-S):** This command switches the normal traffic from the working channels to the protection channels of that span. This switch occurs regardless of the state of the protection channels, unless the protection channels are satisfying a higher priority bridge request, or a signal failure (or a K-byte failure) exists on the protection channels of the span. + +**Manual Switch to protection - Ring (MS-R):** This command performs the ring switch of the normal traffic from the working channels to the protection channels for the span between the node at which the command is initiated and the adjacent node to which the command is destined. This occurs if the protection channels are not in an SD condition and are not satisfying an equal or higher priority bridge request (including failure of the protection channels). + +**Manual Switch to protection - Span (MS-S):** This command switches the normal traffic from the working channels to the protection channels for the same span over which the command is initiated. This occurs if the protection channels are not in an SD condition and are not satisfying an equal or higher priority bridge request (including failure of the protection channels). + +**Exercise - Ring (EXER-R):** This command exercises ring protection switching of the requested channel without completing the actual bridge and switch. The command is issued and the responses are checked, but no normal traffic is affected. + +**Exercise - Span (EXER-S):** This command exercises span protection of the requested channel without completing the actual bridge and switch. The command is issued and the responses are checked, but no normal traffic is affected. + +**NOTE –** Undetected failures are a concern since they do not manifest themselves until a switch is made. This situation makes the protection facility unavailable when it is most needed. In a MS shared protection ring, because the protection facility is shared among all the nodes on the ring, the exerciser function is even more essential. An undetected failure in one span makes ring switching impossible for all the spans on the ring. Thus, the probability of having undetected failures is reduced by exercising the protection switch controller. If a controller failure is detected during an exercise or any diagnostic routine, unless the failure is service affecting, no protection switching request is initiated. An alarm is generated to facilitate prompt repair. + +#### 7.2.4.2 Automatically initiated commands + +APS requests are also initiated based on multiplex section and equipment performance criteria detected by the NE. All the working and protection channels are monitored regardless of the failure or degradation conditions (i.e. after a switch has been completed, all appropriate performance monitoring is continued). The NE initiates the following bridge requests automatically: Signal Failure (SF), Signal Degrade (SD), Reverse Request (RR), and Wait to Restore (WTR). The bridge requests are transmitted from NE to NE (not from OS to NE). + +The SF bridge request is used to protect normal traffic affected by defects, while the SD bridge request is used to protect against signal degradations due to bit errors. The bridge requests are transmitted on both the short and long paths. Each intermediate node verifies the destination node ID of the long-path bridge request and relays the bridge request. The destination node receives the bridge request, performs the activity according to the priority level, and sends the bridged indication. + +The WTR bridge request is used to prevent frequent oscillation between the protection channels and the working channels. The intent is to minimize oscillations, since hits are incurred during switching. The WTR bridge request is issued after the clearing of the defect condition on the working channels. The WTR is issued only after an SF or an SD condition and, thus, does not apply for externally initiated commands. + +The definitions of the automatically initiated bridge requests and their trigger conditions are provided below. + +**Signal Fail - Span (SF-S):** An SF is defined as the presence of the TSFprot condition generated by the MS Trail Termination function defined in Recommendation G.783. The tail-end detects the failure and generates the bridge request. For four-fibre rings, if the failure affects only the working channels, traffic can be restored by switching to the protection channels on the same span. The SF-S bridge request is used to initiate span switching for an SF on the working channels of a four-fibre ring. + +**Signal Fail - Ring (SF-R):** For two-fibre rings, all SFs (as defined previously for span switching) are protected using the ring switch. For four-fibre rings, the ring switch is used only if traffic cannot be restored using span switching. If failures exist on both the working and protection channels within a span, it is necessary to initiate a ring bridge request. Hence, this command is used to request ring switching for signal failures. For a four-fibre ring, a SF-R results from the combination of LOW-S and a detected or received working line failure on the same span or the following combination of detected or received conditions on the working and protection lines: + +- working line failed and protection line failed on the same span; +- working line failed and protection line degraded on the same span; +- working line degraded and protection line failed on the same span. + +**Signal Fail - Protection (SF-P):** This command is used to indicate to an adjacent node that the protection channels are in a Signal Fail state (as defined previously for span switching). A signal failure of the protection channels is equivalent to a lockout of protection for the span that is affected by the failure. Hence, the K1 byte that is transmitted to the adjacent node is the same code as that of a Lockout of Protection - Span. SF-P is used only for four-fibre rings. + +**Signal Degrade - Span (SD-S):** Signal Degrade is defined as the presence of the TSD condition generated by the MS Trail Termination function defined in Recommendation G.783. In four-fibre rings, the working channels on the degraded span can be protected using the protection channels on the same span. This bridge request is used to switch the normal traffic to the protection channels in the same span where the failure is located. + +**Signal Degrade – Ring (SD-R):** For two-fibre rings, any degraded multiplex section is protected using the ring switch (Degradation is defined above under Signal Degrade - Span). For four-fibre rings, a SD-R results from the combination of LOW-S and a detected or received working line degrade on the same span or the combination of detected or received signal degrade conditions on the working and protection lines on the same span. + +**Signal Degrade - Protection (SD-P):** This command is used when an NE detects a degradation on its protection channels, and there are no higher priority bridge requests existing on the working channels (Degradation is defined above under Signal Degrade - Span). This bridge request is used only for four-fibre rings. + +**Reverse Request - Span (RR-S):** This command is transmitted to the tail-end NE as an acknowledgment for receiving the short-path span bridge request. It is transmitted on the short path only. + +**Reverse Request - Ring (RR-R):** This command is transmitted to the tail-end NE on the short path as an acknowledgment for receiving the short-path ring bridge request. + +**Wait-To-Restore (WTR):** This command is issued when working channels meet the restoral threshold after an SD or SF condition. It is used to maintain the state during the WTR period unless it is pre-empted by a higher priority bridge request. + +### 7.2.5 Protection switch protocol + +Two APS bytes, K1 and K2, shall be used for protection switching. See 7.2.6 for details on the operational usage of these bytes. + +Bytes K1 and K2 shall be transmitted within the multiplex section overhead of the STM-N that is carrying the protection channels. Note, however, that bits 6-8 of byte K2 are used on all STM-N line signals to signal MS-RDI and MS-AIS. + +APS bytes shall be accepted as valid only when identical bytes are received in three consecutive frames. + +#### 7.2.5.1 Byte K1 + +These bits shall be assigned as per Table 7-7. K1 bits 1-4 carry bridge request codes, listed in descending order of priority in Table 7-7. K1 bits 5-8 carry the destination node ID for the bridge request code indicated in K1 bits 1-4. + +**Table 7-7/G.841 – Byte K1 functions** + +| Bridge Request code (Bits 1-4) | | Destination Node Identification (Bits 5-8) | +|----------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bits | | | +| 1 2 3 4 | | | +| 1 1 1 1 | Lockout of Protection (Span) LP-S or Signal Fail (Protection) | | +| 1 1 1 0 | Forced Switch (Span) FS-S | | +| 1 1 0 1 | Forced Switch (Ring) FS-R | | +| 1 1 0 0 | Signal Fail (Span) SF-S | | +| 1 0 1 1 | Signal Fail (Ring) SF-R | | +| 1 0 1 0 | Signal Degrade (Protection) SD-P | | +| 1 0 0 1 | Signal Degrade (Span) SD-S | | +| 1 0 0 0 | Signal Degrade (Ring) SD-R | | +| 0 1 1 1 | Manual Switch (Span) MS-S | | +| 0 1 1 0 | Manual Switch (Ring) MS-R | | +| 0 1 0 1 | Wait-To-Restore WTR | | +| 0 1 0 0 | Exerciser (Span) EXER-S | | +| 0 0 1 1 | Exerciser (Ring) EXER-R | | +| 0 0 1 0 | Reverse Request (Span) RR-S | | +| 0 0 0 1 | Reverse Request (Ring) RR-R | | +| 0 0 0 0 | No Request NR | | +| | | The destination node ID is set to the value of the ID of the node for which that K1 byte is destined. The destination node ID is always that of an adjacent node (except for default APS bytes). | +| NOTE – Reverse Request assumes the priority of the bridge request to which it is responding. | | | + +#### **7.2.5.2 Byte K2** + +Byte K2 shall be assigned as shown in Table 7-8. + +**Table 7-8/G.841 – Byte K2 functions** + +| Source node identification (Bits 1-4) | Long/Short (Bit 5) | Status (Bits 6-8) | +|----------------------------------------------|---------------------------|--------------------------------------------| +| | Bit | Bit | +| | 5 | 6 7 8 | +| | 0 Short path code (S) | 1 1 1 MS-AIS | +| | 1 Long path code (L) | 1 1 0 MS-RDI | +| | | 1 0 1 Reserved for future use | +| | | 1 0 0 Reserved for future use | +| | | 0 1 1 Extra Traffic on protection channels | +| | | 0 1 0 Bridged and Switched (Br&Sw) | +| | | 0 0 1 Bridged (Br) | +| | | 0 0 0 Idle | +| Source node ID is set to the node's own ID. | | | + +### 7.2.6 Protection algorithm operation + +This subclause is structured as follows: + +First, a number of general APS algorithm rules are given. Detailed rules then follow. Subclause 7.2.6.1 covers the three classes of ring node APS states, and the steady-state behavior of the node in these states. Subclause 7.2.6.2 describes the transition rules among the different ring node APS states. + +These rules apply conceptually to a single MS shared protection ring APS controller operating at a node. It is choosing switching and signalling actions for both sides of the node based on all incoming K-byte signalling from both directions, detected failures on both sides, local equipment failures, and externally initiated commands. In general, this conceptual controller looks at all incoming information, chooses the highest priority input, and takes action based on that choice. + +Figure 7-9 illustrates the conceptual operation of an MS shared protection ring APS controller. + + + +The diagram shows a central rectangular box labeled "APS controller". Four other rectangular boxes are positioned around it, with arrows pointing from each towards the central box. The boxes are: "Externally initiated commands" (top), "Detected failures (both sides)" (left), "Local equipment failures" (right), and "Incoming K-byte signalling (both sides)" (bottom). Each arrow has a small 'X' mark on it near the central box, indicating that the inputs are being processed or filtered by the controller. + +Conceptual MS shared protection ring APS controller diagram + +T1516840-94 + +**Figure 7-9/G.841 – Conceptual MS shared protection ring APS controller** + +The following set of general rules apply: + +**Rule G #1 – BRIDGE REQUEST VALIDATION** (Bridge request and bridge request status definitions): + +**Rule G #1a:** (Bridge request) The information contained in byte K1 bits 1-4 shall be considered as a bridge request if: + +- these bits indicate one of the ring bridge request codes and byte K2 bit 5 indicates a long path code; or +- these bits indicate one of the ring bridge request codes and byte K2 bit 5 indicates a short path code; or +- these bits indicate one of the span bridge request codes and byte K2 bit 5 indicates a short path code. + +**Rule G #1b:** (Bridge request status) The information contained in byte K1 bits 1-4 shall be considered as a bridge request status if: + +- these bits indicate one of the span bridge request codes and byte K2 bit 5 indicates a long path code. + +**Rule G #1.c:** When a four-fibre ring node is in a SF-R or SD-R condition, and the SF-R or SD-R request can not be signalled because it is not allowed to coexist with other higher priority APS requests at that node, the node shall consider the detected or received protection line condition as a second input to the APS controller. + +The relationship among bridge request codes, bridge request status information, and K-byte indications is shown in Table 7-9. + +**Table 7-9/G.841 – Relationships between K2 bit 5 and K1 bits 1-4** + +| K2 bit 5 code | K1 bits 1-4 | | +|---------------|------------------|-----------------------| +| | Ring bridge code | Span bridge code | +| Long path | Bridge request | Bridge request status | +| Short path | Bridge request | Bridge request | + +Note that the MS-RDI and MS-AIS signals terminate at multiplex section terminating elements as specified in Recommendation G.783. + +#### 7.2.6.1 Ring node APS state + +There are three classes of ring node states: the idle state, the switching state, and the pass-through state. + +##### 7.2.6.1.1 Idle state + +A node is in the idle state when it is not sourcing or receiving any APS requests or bridge request status and it is receiving Idle or ET codes from both directions. + +**Rule I #1 – IDLE STATE SOURCED K-BYTES:** + +**Rule I #1a:** Any node in the idle state not inserting, dropping, or passing through extra traffic shall source the K-bytes in both directions as given in Table 7-10. + +**Table 7-10/G.841 – Byte K1 and K2 values sourced in the idle state** + +| | | | +|----------|---|------------------------| +| K1 [1-4] | = | 0000 (No Request code) | +| K1 [5-8] | = | Destination node ID | +| K2 [1-4] | = | Source node ID | +| K2 [5] | = | 0 (short path code) | +| K2 [6-8] | = | 000 (idle code) | + +**Rule I #1b:** Any node in the idle state inserting, dropping, or passing through extra traffic shall source the K-bytes shown in Table 7-10 with the exception that byte K2 bits 6-8 transmitted over any span that contains extra traffic shall have the value 011 (Extra Traffic code). + +Until the node has knowledge of the ring map, it shall behave as per Rule I-S #3. Signalling in the start-up state is for further study. + +**Rule I #2** – IDLE STATE RECEIVED K-BYTES: Any node in the idle state shall terminate K1 and K2 in both directions. + +##### 7.2.6.1.2 Switching state + +It is understood that a node not in the idle or pass-through states is in the switching state. This includes the default signalling status, e.g. node start-up, where there is no ring map available. + +**Rule S #1** – SWITCHING STATE SOURCED K-BYTES: + +**Rule S #1a:** Any node in the switching state shall source K-bytes as shown in Table 7-11: + +**Table 7-11/G.841 – Byte K1 and K2 values +sourced by a node in the switching state** + +| | | | +|----------|---|------------------------------| +| K1 [1-4] | = | Bridge Request (Status) code | +| K1 [5-8] | = | Destination node ID | +| K2 [1-4] | = | Source node ID | +| K2 [5] | = | 0/1 (short/long path code) | +| K2 [6-8] | = | Status code | + +**Rule S #1b:** Any node in the switching state (for either span or ring bridge requests) shall source a bridge request on the short path and a bridge request (or bridge request status) on the long path. Both the bridge request and the bridge request status have the same priority (or one of them is a Reverse Request), and protect the same span. Exceptions to this can occur when there are more than one switch requests active at a node. The exceptions are as follows: + +- The isolated node cases described in Rules S #1c and S #1d. +- The case of a span bridge request on each side of the node, the node shall source a bridge request on each short path, where the status bits indicate the state of the bridge and switch for the corresponding span. +- The case of a ring bridge request pre-empting a span bridge request on an adjacent span as described in Rule S-S #2b. +- Cases where SF-P and SD-P coexist with a ring switch on the same span. Table 7-12 defines the signalling for these cases. + +**Table 7-12/G.841 – SD-P and SF-P coexisting with ring switches on the same span** + +| Highest priority ring request | Short-path conditions | | Priority signalled on short path | +|-------------------------------|-----------------------|-----------------------|----------------------------------| +| | Working | Protection | | +| FS-R | clear, SD, or SF | SF | LP-S | +| FS-R | clear, SD, or SF | SD | SD-P | +| FS-R | clear, SD, or SF | LP-S or SD-P (K-byte) | RR-S | +| SF-R(K-byte) | clear | SF | LP-S | +| SF-R(K-byte) | clear or SD | SD | SD-P | +| SD-R(K-byte) | clear | SD | SD-P | +| MS-R or EXER-R | clear | SF | LP-S | +| MS-R or EXER-R | clear | SD | SD-P | +| MS-R or EXER-R | clear | LP-S or SD-P (K-byte) | RR-S | + +**Rule S #1c:** Whenever a node in the switching state terminates a new short-path K-byte bridge request from an adjacent node, of equal or higher priority than the bridge request it is currently executing, over the same span, it shall source a bridge request of the same priority on the corresponding long path. Whenever a node receives ring bridge requests on both short paths from its adjacent nodes, the long-path bridge request shall be signalled rather than the short-path reverse requests. This rule takes precedence over Rule S #1b in case of multiple bridge requests at the same node [see Figure 7-10 a)]. + +**Rule S #1d:** Whenever a node detects a condition requiring a ring switch or an externally initiated command for a ring switch applied at that node, it shall always source over the short path a short-path ring bridge request as long as the ring bridge request is not pre-empted by a higher priority bridge request [See Figure 7-10 b)]. This rule takes precedence over Rule S #1c. Note that whenever a node receives in one direction a short-path ring bridge request on one side and detects one of the above-mentioned conditions on the other side, it shall signal the bridge request associated with that condition [see Figure 7-10 c)]. + +**Rule S #1e:** A node in the switching state shall insert the ET code in K2 bits 6-8 on spans that are carrying extra traffic. + +**Rule S #2 – SWITCHING STATE RECEIVED K-BYTES:** Any node in the switching state shall terminate K1 and K2 in both directions. + +**Rule S #3 – UNIDIRECTIONAL BRIDGE REQUEST ACKNOWLEDGMENT:** As soon as it receives a bridge request or bridge request status, the node to which it is addressed shall acknowledge the bridge request by changing K1 bits 1-4 to the Reverse Request code on the short path, and to the received bridge request priority on the long path. + +**Rule S #4 – ALLOWED COEXISTING COMPLETED PROTECTION SWITCHES:** + +**Rule S #4a:** The following switches are allowed to coexist: + +- SD-P with any span switch; +- LP-S or SF-P with any span switch for other spans; +- SF-P or SD-P with any ring switch on the same span; +- LP-S with SD-P; +- LP-S with LP-S; + +- SD-P with SD-P; +- FS-R with FS-R (ring split into multiple subrings); +- SF-R with SF-R (ring split into multiple subrings); +- FS-R with SF-R (ring split into multiple subrings); +- Any span switch with any other span switch. + +**Rule S #4b:** When multiple equal priority bridge requests over different spans of SD-R, MS-R, or EXER-R exist at the same time, no bridge or switch shall be executed and existing switches and bridges shall be dropped. (Note that in case of multiple SD-R failures, all failures will be reported or alarmed. However, this behaviour can be considered as expected by the user.) The nodes shall signal the ring bridge request in byte K1, and byte K2 bits 6-8 shall be set to Idle. + +**Rule S #5 – LOSS OF RING BRIDGE REQUEST:** If a node executing a ring bridge and switch no longer receives a valid ring bridge request on the long path, it shall drop its ring bridge and switch, and shall signal and act based on its highest priority input. + +**Rule S #6 – LOSS OF SPAN BRIDGE REQUEST:** If a node executing a span bridge and switch no longer receives a valid span bridge request (on the short path), it shall drop its span bridge and switch, and shall signal and act based on its highest priority input. + +**Rule S #7 – EXTRA TRAFFIC:** A node in the switching state shall not pass through extra traffic, unless it is in the switching state due to a LP-S (signal fail - protection), or a SD-P request. A node in the switching state due to a WTR for a span switch, or any span request, except LP-S, SD-P, or EXER-S, shall not source or terminate extra traffic on the short path of that bridge request. A node in the switching state due to WTR for a ring switch, or any ring request, except EXER-R, shall not source or terminate extra traffic. + +**Rule S #8 – WTR TERMINATION:** Whenever a node in the WTR state drops its bridge and switch before the WTR timer expires, it shall immediately terminate the WTR and act based on its highest priority input. + +**Rule S #9 –** A node in a ring switching state that receives the external command LOW-R for the affected span shall drop its bridge and switch and shall signal No Request, SF-P, or SD-P. Upon the reception of No Request in combination with either Idle or ET code or bridge request status from the span away from the LOW-R span, the node shall re-insert extra traffic that was pre-empted on that span. + + + +K1:[SF-R/C] K1:[SF-R/C] K1:[SF-R/D] K1:[SF-R/B] K1:[SF-R/C] K1:[SF-R/C] + K2:[B/L/Idle] K2:[B/S/RDI] K2:[C/L/Idle] K2:[C/L/Idle] K2:[D/S/RDI] K2:[D/L/Idle] + +a) Node C is told of cuts + +K1:[SF-R/C] K1:[RR-R/C] K1:[SF-R/B] K1:[SF-R/D] K1:[RR-R/C] K1:[SF-R/C] + K2:[B/L/Idle] K2:[B/S/Idle] K2:[C/S/RDI] K2:[C/S/RDI] K2:[D/S/Idle] K2:[D/L/Idle] + +b) Node C detects cuts + +K1:[SF-R/C] K1:[RR-R/C] K1:[SF-R/B] K1:[SF-R/B] K1:[SF-R/C] K1:[SF-R/C] + K2:[B/L/Idle] K2:[B/S/Idle] K2:[C/S/RDI] K2:[C/L/Idle] K2:[D/S/RDI] K2:[D/L/Idle] + +c) Node C is told of cut on one side and detects cut on the other + +T1516850-94 + +—————→ Working channels + .....→ Protection channels + +Figure 7-10/G.841 – Isolated node signalling. The diagram shows three nodes: Node B, Node C (shaded), and Node D. Solid lines represent working channels, and dotted lines represent protection channels. Arrows indicate the direction of K1 and K2 bytes. 'X' marks indicate cuts in the channels. Part (a) shows Node C being told of cuts on both sides. Part (b) shows Node C detecting cuts on both sides. Part (c) shows Node C being told of a cut on one side and detecting one on the other. Below the diagrams is a legend: a solid line with an arrow for 'Working channels' and a dotted line with an arrow for 'Protection channels'. + +Figure 7-10/G.841 – Isolated node signalling (signalling states prior to nodes B and D establishing a ring bridge and switch) + +##### 7.2.6.1.3 Pass-through state + +A node is in the pass-through state when its highest priority APS request is a bridge request or bridge request status not destined to or sourced by itself. The pass-through can be either unidirectional or bidirectional, depending on its nature. There are three types of pass-through: unidirectional full pass-through, bidirectional full pass-through, and K-byte pass-through (see clause 3 for the definition of the different kinds of pass-through). + +**Rule P #1 – PASS-THROUGH STATE SOURCED AND RECEIVED K-BYTES:** When a node is in pass-through, it transmits on one side, all or part of the K1 and K2 bytes which it receives from the other side. A node in the K-byte pass-through state shall source the ET code in bits 6-8 on spans that are carrying extra traffic. A K-byte pass-through node receiving the Extra Traffic code shall + +source Idle in the opposite direction if no extra traffic exists on the opposite span. A node in unidirectional full pass-through shall continue sourcing the previously sourced K-bytes in the opposite direction, with the exception that K2 bits 6-8 shall reflect the appropriate status code. + +**Rule P #2 – REMAINING IN THE PASS-THROUGH STATE DURING SIGNALLING TRANSITIONS:** When a node that is in a pass-through state receives a long path ring bridge request destined to itself, and another long path ring bridge request of the same priority destined to another node, the node shall not transit to another state (This rule is necessary for the clearing sequence of the node failure condition. See Figure I.5.) + +**Rule P #3 – EXTRA TRAFFIC:** A node in full pass-through shall not source or terminate extra traffic. A node that is in the K-byte pass-through state can source, terminate, and pass-through extra traffic. + +#### 7.2.6.2 Ring node APS state transition rules + +Subclause 7.2.6.1 described the three ring node states. This subclause describes the transition rules among these different states. Note that, as in linear APS, the following basic rules apply: + +**Rule Basic #1 – STATE TRANSITION TRIGGERS:** All state transitions are triggered by an incoming K-byte change, a WTR expiration, an externally initiated command, or locally detected multiplex section or equipment performance criteria. + +**Rule Basic #2 – K-BYTE VALIDATION:** Before accepting the K-bytes as valid, the value shall be received identically in three successive frames. + +**Rule Basic #3 – K2 BITS 6-8 UPDATE:** All bridge and switch actions shall be reflected by updating byte K2 bits 6-8, unless an MS-RDI condition exists, or the span is carrying extra traffic. An MS-RDI condition shall cause the MS-RDI code to override all other codes in byte K2 bits 6-8 on the failed span (except for MS-AIS) regardless of the state of the bridge and switch. MS-RDI and MS-AIS terminate at multiplex section terminating elements as specified in Recommendation G.783. A node shall signal the ET code on any span that is carrying extra traffic. + +**Rule Basic #4 – APS requests** due to a locally detected failure, an externally initiated command, or received K-bytes shall pre-empt APS requests in the prioritized order given in Table 7-7, unless the bridge requests are allowed to coexist. Actions resulting from incoming bridge requests shall take priority over actions resulting from incoming bridge request status signalling regardless of the priority of each. Bridge request status signalling shall never pre-empt a bridge request. + +##### 7.2.6.2.1 Transitions between the idle and pass-through states + +**Rule I-P #1 – TRANSITION FROM THE IDLE STATE TO THE PASS-THROUGH STATE:** + +**Rule I-P #1a:** The transition from the idle state to the full or K-byte pass-through states shall be triggered by a valid K-byte change, in any direction, from the No Request code to any other bridge request code, as long as the new bridge request is not destined for the node itself. Both directions move then into full or K-byte pass-through, according to Rule I-P #1b. + +**Rule I-P #1b:** For any span bridge request status or the EXER-R bridge request, the intermediate nodes on the long path shall go into K-byte pass-through. Actions taken at an intermediate node upon receiving a valid ring bridge request other than EXER-R are: + +- for NEs without extra traffic, when the node in the idle state receives a valid ring bridge request in any direction that is not destined for the node itself, the node shall enter the bidirectional full pass-through state; + +- for NEs with extra traffic, when the node in the idle state receives a valid ring bridge request in any direction that is not destined for the node itself, the node shall drop extra traffic bidirectionally, and shall enter unidirectional full pass-through, in the direction of the bridge request only. Upon receiving the crossing K-bytes, the node shall enter bidirectional full pass-through. + +**Rule I-P #2** – TRANSITION FROM THE PASS-THROUGH STATE TO THE IDLE STATE: A node shall revert from any pass-through state to the idle state when it detects No Request codes in K1 bits 1-4 and Idle or ET codes in K2 bits 6-8, from both directions. Both directions revert simultaneously from the pass-through state to the idle state. Extra traffic that was pre-empted shall be re-inserted and the ET code sourced as defined in Rule I #1b. + +##### 7.2.6.2.2 Transitions between the idle and switching states + +**Rule I-S #1** – TRANSITION FROM THE IDLE STATE TO THE SWITCHING STATE: + +**Rule I-S #1a:** Transition of an NE from the idle state to the switching state shall be triggered by one of the following conditions: + +- a valid K-byte change from the No Request (NR) code to any ring bridge request code received on either the long path or the short path and destined to that NE; +- a valid K-byte change from the NR code to any span bridge request code received on the short path and destined to that NE; +- an externally initiated command for that NE; +- the detection of a failure at that NE. + +**Rule I-S #1b:** Actions taken at a switching NE upon receiving a valid bridge request are (Note that in order to execute a ring bridge and switch, the bridge request shall be received on the long path. See Rule I-S #1c): + +- for FS-R bridge requests, the node shall check if there is any need for squelching and squelch accordingly, execute a bridge and insert the Bridged code in K2 bits 6-8 in both directions (with MS-RDI and MS-AIS exceptions). Upon receiving a Bridged code in byte K2 bits 6-8 on the bridge request path, the NE shall execute a switch and update K2 bits 6-8 on both paths accordingly; +- for SF-R bridge requests, the node shall check if there is any need for squelching and squelch accordingly, execute a bridge and switch, and insert in byte K2 bits 6-8 the Bridged and Switched code on both the long and the short path (with MS-RDI and MS-AIS exceptions); +- for all other bridge requests, except SD-P, EXER-S, EXER-R, and LP-S, the node shall execute a bridge and insert the Bridged code in byte K2 bits 6-8 in both directions (with MS-RDI and MS-AIS exceptions). Upon receiving a Bridged code in byte K2 bits 6-8 on the bridge request path, the NE shall execute a switch and update K2 bits 6-8 on both paths accordingly; +- for SD-P, EXER-S, EXER-R, and LP-S, the node shall signal as for any other bridge request, but shall not execute the bridge or switch. See 7.2.1.2. +- Extra traffic shall be dropped immediately on all spans for a ring switch, or on the span whose protection channels are required for a span switch. +- no bridge or switch shall be executed while the ET code is received on the span whose protection channels are required by that bridge and switch. + +**Rule I-S #1c:** A span switch shall be put up or brought down only with short-path bridge requests. A ring switch shall be put up or brought down only with long-path bridge requests. + +**Rule I-S #2** – TRANSITION FROM THE SWITCHING STATE TO THE IDLE STATE: A node shall revert from the switching state to the idle state when it detects NR codes in byte K1 bits 1-4 and Idle or ET codes in byte K2 bits 6-8 from both directions. The transition from the switching state to the idle state shall be a three-step transition. + +- Step 1: When a WTR time expires or an externally initiated command is cleared at a node, and the node receives a Reverse Request from the short span, the node shall drop its switch, and signal the No Request code in byte K1 bits 1-4, and the Bridged code in byte K2 bits 6-8. (Note that this step may be executed in transitions from the switching state to the pass-through state.) +- Step 2: Upon reception of the No Request code, and of the indication that the switch has been dropped, the head-end node shall drop its bridge and its switch, and source the Idle code in both directions. The indication that the switch has been dropped is received on the short path for span bridge requests, and on the long path for ring bridge requests. +- Step 3: Once the tail-end detects incoming Idle codes, it shall also drop its bridge and switch and source the Idle code in both directions. Extra traffic that was pre-empted shall be re-inserted and the ET code sourced as defined in Rule I #1b. An LP S code due to a signal fail - protection, that was pre-empted, shall be re-inserted. +- Step 4: Once the head-end detects incoming Idle or ET codes from both directions, it shall revert to the idle state. Extra traffic that was pre-empted shall be re-inserted and the ET code shall be sourced as defined in Rule I #1b. A LP-S code due to a signal fail - protection that was pre-empted shall be re-inserted. +- Note that there are cases in which no bridge or switch is to be executed due to other conditions on the ring. In these cases, the NE that initiated the request (i.e. tail-end) shall signal the No Request code. Upon reception of the No Request code, the head-end shall also source the Idle code. + +**Rule I-S #3** – A node shall transmit the default APS code until it is capable of proper APS signalling in accordance with the current state of the ring. The default APS code shall be used to indicate that the node can not properly signal APS bytes, and therefore cannot properly execute protection switching. + +**Rule I-S #4** – A ring (span) switching node receiving the default APS code on the short (long) path shall not change its signalling or take any action associated with that path until proper APS codes are received. A ring (span) switching node receiving default APS code on the long (short) path shall drop its bridge and switch. + +**Rule I-S #5** – A switching node that is not bridged or switched that receives long-path ring bridge requests destined to itself from both of its neighbours shall take no action based on these bridge requests. + +**Rule I-S #6** – If a switching node receives from both directions the APS bytes that it is sourcing, and receives no other APS request, it shall transition to the idle state. Otherwise, the switching node shall signal according to its highest priority input. + +**Rule I-S #7** – When a node receives a Reverse Request code over the span which it is protecting, and when that same node is sending a Reverse Request code, it shall drop its bridge and switch as described in Rule I-S #2, except for bridge request status or bridge requests of signal failure and signal degrade priority. For signal failure and signal degrade, the node shall drop the switch and the bridge after the expiration of the WTR time according to Rule S-S #3. + +##### 7.2.6.2.3 Transitions between switching states + +This subclause first provides a set of requirements and objectives with which each ring node shall comply to be able to perform a switch without creating misconnections, and then provides the set of rules necessary to coordinate a transition between switching states. + +###### 7.2.6.2.3.1 Ring map and squelch table information + +Each node on a ring shall maintain a ring map describing the ring connectivity, and a local squelch table indicating the source and destination of all added, dropped, and pass-through AU-3/4s. + +###### 7.2.6.2.3.2 Squelching + +AU-3/4 squelching shall be performed at the switching nodes by inserting AU-AIS. + +The switching node shall, by comparing K-byte addresses (crossing K-bytes) to the information contained in the ring map, identify which nodes are missing. From this information and the squelch table, it shall identify which AU-3/4s are added and dropped at these nodes and shall squelch them bidirectionally. + +###### 7.2.6.2.3.3 Transition rules + +The following transition rules apply: + +###### **Rule S-S #1 – TRANSITION FROM THE SWITCHING STATE TO THE SWITCHING STATE:** + +**Rule S-S #1a:** When an NE that is currently executing an SF-R switch receives another SF-R or FS-R bridge request over the long path not destined to that NE, the NE shall check if there is any need for squelching and squelch accordingly. The NE shall stop squelching when the bridge and switch are dropped. + +**Rule S-S #1b:** When an NE that is currently executing an FS-R switch receives another FS-R or SF-R bridge request over the long path not destined to that NE, the NE shall check if there is any need for squelching and squelch accordingly. The NE shall stop squelching when the bridge and switch are dropped. + +**Rule S-S #1c:** When an NE that is currently executing any ring switch receives a higher priority ring APS request (due to a locally detected failure, an externally initiated command, or a ring bridge request destined to it) for the same span, it shall upgrade the priority of the ring switch it is executing to the priority of the received ring bridge request. + +**Rule S-S #1d:** When an NE that is currently executing any span switch receives a higher priority span APS request (due to a locally detected failure, an externally initiated command, or a span bridge request destined to it) for the same span, it shall upgrade the priority of the span switch it is executing to the priority of the received span bridge request. + +**Rule S-S #1e:** When a NE that is currently executing an EXER-R request receives a higher priority ring APS request (due to a locally detected failure, an externally initiated command, or a ring bridge request destined to it) for the same span, it shall remove any extra traffic. The node shall then execute the new ring APS request as detailed in Rule I-S #1. + +**Rule S-S #1f:** When a NE that is currently executing an EXER-S request receives a higher priority span APS request (due to a locally detected failure, an externally initiated command, or a ring bridge request destined to it) for the same span, with the exception of LP-S and SD-P, it shall remove any extra traffic from the short path. It shall then signal the new span bridge request with the Idle code in K2 bits 6-8 on the short path, and the new span bridge request on the long path. If there is extra traffic on the long path, the ET code shall be signalled in K2 bits 6-8. The node shall then execute the new span APS request as detailed in Rule I-S #1. + +###### **Rule S-S #2 – SWITCH PRE-EMPTION:** + +**Rule S-S #2a:** When an NE that is currently executing a span switch receives a ring APS request (due to a locally detected failure, an externally initiated command, or a ring bridge request destined to it) destined to it of greater priority for the same span, it shall: + +- drop the span bridge and switch immediately; +- execute the ring APS request (as detailed in Rule I-S #1). + +**Rule S-S #2b:** When a node that is currently executing a span switch receives a ring APS request (due to a locally detected failure, an externally initiated command, or a ring bridge request destined to it) destined to it for its adjacent span of greater priority than the span switch it is executing, it shall drop the span switch, signal No Request in K1 and Bridged in K2 in the direction of the span APS request, and signal the ring request in K1 and Idle in K2 in the direction of the ring APS request. + +**Rule S-S #2c:** When a node that is currently executing a span switch receives a long-path ring bridge request for a non-adjacent span of greater priority than the span switch it is executing, it shall drop the span switch and signal No Request in K1 and Bridged in K2 in both directions. + +**Rule S-S #2d:** If a span switching node that is bridged and switched receives a No Request and an indication that the switch has been dropped for that span, the node shall drop its bridge and switch, and, if the node's highest priority input is: + +- a span bridge request status destined to the node itself, or No Request, then the node shall source No Request in K1 and Idle in K2 in both directions; +- a span APS request (due to a locally detected failure, an externally initiated command, or a span bridge request destined to it) for an adjacent span, then the node shall signal in accordance with that request; +- a ring APS request (due to a locally detected failure, an externally initiated command, or a ring bridge request destined to it) for an adjacent span, then the node shall execute the ring bridge request; +- a long-path ring APS request destined to another node, then the node shall signal in accordance with either Rule S-P #1a or S-P #1b, depending upon whether or not the Bridged indication is being received; +- a span bridge request status destined to another node, then the node shall signal in accordance with either Rule S-P #1c or S-P #1d, depending upon whether or not the Bridged indication is being received; +- a span APS request (due to a locally detected failure or externally initiated command) for the same span, the node shall signal the span bridge request in K1 and Idle in K2. + +**Rule S-S #2e:** If a span switching node that is bridged receives a No Request and an indication that the switch has been dropped for that span, the node shall drop its bridge, and, if the node's highest priority input is: + +- a span bridge request status destined to the node itself, or No Request, then the node shall source No Request in K1 and Idle in K2 in both directions; +- a span APS request (due to a locally detected failure, an externally initiated command, or a span bridge request destined to it) for an adjacent span, then the node shall signal in accordance with that request; +- a ring APS request (due to a locally detected failure, an externally initiated command, or a ring bridge request destined to it) for an adjacent span then the node shall execute that request; + +- a long path ring bridge request destined to another node, then the node shall signal in accordance with either Rule S-P #1a or S-P #1b, depending up whether or not the Bridged indication is being received; +- a span bridge request status destined to another node, then the node shall signal in accordance with either Rule S-P #1c or S-P #1d, depending on whether or not the Bridged indication is being received; +- a span APS request (due to a locally detected failure or externally initiated command) for the same span, the node shall signal the span bridge request in K1 and Idle in K2. + +**Rule S-S #2f:** When an NE that is currently executing a ring switch receives a span or ring APS request (due to a locally detected failure, an externally initiated command, or a span or ring bridge request destined to it) of greater priority for an adjacent span than the ring switch it is executing, it shall: + +- drop the ring bridge and switch immediately; +- execute the higher priority APS request (as detailed in Rule I-S #1). + +**Rule S-S #2g:** When an NE that is currently executing a ring switch receives a span APS request (due to a locally detected failure, an externally initiated command, or a span bridge request destined to it) of greater priority for the same span, it shall: + +- drop the ring bridge and switch immediately; +- execute the span APS request. + +**Rule S-S #2h:** For a four-fibre ring: If a ring switching node receives an APS request of higher priority than the ring APS request it is executing, and the two requests are not allowed to coexist, the node shall drop the lower priority request and consider its detected or received protection line condition in addition to the higher priority request. If the detected or received request for the protection line is allowed to coexist with the higher priority APS request, and if either the higher priority APS request is for a span switch on the adjacent span to the detected or received protection channel request, or if the higher priority APS request is for a ring switch for the same span as the detected or received protection channel request, then the node shall respond to both the protection channel request and the higher priority APS request on the respective spans. This rule takes precedence over Rule S-S #1c and Rule S-S #2f. + +###### **Rule S-S #3 – RING AND SPAN SWITCH CLEARING (NO PRE-EMPTION):** + +**Rule S-S #3a:** When a failure condition clears at a node, the node shall enter Wait-To-Restore and remain in Wait-To-Restore for the appropriate time-out interval, unless: + +- 1) a different bridge request of higher priority than WTR is received; or +- 2) another failure is detected; or +- 3) an externally initiated command becomes active. + +The node shall send out a WTR code on both the long and short paths. + +**Rule S-S #3b:** When a node that is executing a switch in response to an incoming SD-S, SD-R, SF-S, or SF-R bridge request (not due to a locally detected failure) receives a Wait-To-Restore code (unidirectional failure case), it shall send out Reverse Request on the short path and WTR on the long path. + +**Rule S-S #4 – SPAN SWITCH TIME-OUT:** For a four-fibre ring, when it is not possible to execute an SD-S or SF-S bridge request because no acknowledgment is received on the short path (time-out, whose duration is an equipment issue), or because the protection channels become unavailable, including degradation or failure of the protection line or LOW-S, the appropriate ring switch shall be attempted. + +**Rule S-S #5** – A switching node that receives ring bridge requests destined to itself from both of its neighbours shall drop its bridge and switch. + +**Rule S-S #6** – When an NE that is currently receiving an LP-S bridge request or is sourcing an LP-S bridge request because of a signal fail - protection receives an externally initiated ring bridge command or detects a failure of the working line for the same span, it shall assume the priority of the ring bridge request. + +##### 7.2.6.2.4 Transitions between switching and pass-through states + +**Rule S-P #1** – SWITCH PRE-EMPTION RULES (Switching State to Pass-Through State): + +**Rule S-P #1a:** If a span switching node that is not bridged or switched is receiving a Bridged code for that span, and its highest priority input is a long-path ring bridge request destined to another node, then the node shall signal No Request in K1 and Idle in K2 in both directions. + +**Rule S-P #1b:** If a span switching node that is not bridged or switched receives an indication that the bridge has been dropped for that span, and its highest priority input is a long path ring bridge request destined to another node, then: + +- for NEs without extra traffic, the node shall enter bidirectional full pass-through; +- for NEs with extra traffic, the node shall drop extra traffic bidirectionally, and shall enter unidirectional full pass-through, in the direction of the bridge request only. Upon receiving the crossing K-bytes, the node shall enter bidirectional full pass-through. + +**Rule S-P #1c:** If a span switching node that is not bridged or switched is receiving a Bridged code for that span, and its highest priority input is a span bridge request status destined to another node, then the node shall signal No Request in K1 and Idle in K2 in both directions. + +**Rule S-P #1d:** If a span switching node that is not bridged or switched receives an indication that the bridge has been dropped for that span, and its highest priority input is a span bridge request status destined to another node, then the node shall enter K-byte pass-through. It shall then reinsert any extra traffic that had been pre-empted. + +**Rule S-P #1e:** When a node that is currently executing a ring switch receives a long-path ring bridge request for a non-adjacent span of greater priority than the ring switch it is executing, it shall drop its bridge and switch immediately, then the node shall enter bidirectional full pass-through. + +**Rule S-P #1f:** When a node that is currently executing a ring switch has as its highest priority input long-path ring bridge requests not destined to itself from both directions, it shall drop its bridge and switch immediately, then the node shall enter bidirectional full pass-through. + +**Rule S-P #1g:** If a ring switching node that is not bridged or switched has as its highest priority input a span bridge request status destined to another node, then the node shall enter K-byte pass-through. It shall then reinsert any extra traffic that had been pre-empted. + +**Rule S-P #2** – PASS-THROUGH TO SWITCHING TRANSITIONS: + +**Rule S-P #2a:** The transition of a node from full pass-through to switching shall be triggered by: + +- 1) an equal, higher priority, or allowed coexisting externally initiated command; +- 2) the detection of an equal, higher priority, or allowed coexisting failure; +- 3) the receipt of an equal, higher priority, or allowed coexisting bridge request destined to that NE; +- 4) the detection of an APS byte sourced by that NE. + +**Rule S-P #2b:** The transition of a node from K-byte pass-through to switching shall be triggered by: + +- 1) any externally initiated command; +- 2) the detection of any failure; +- 3) the receipt of any bridge request destined to that NE. + +**Rule S-P #2c:** If a node that was in the full pass-through state is now sourcing a span bridge request due to Rule S-P #2a, the node shall insert AU-AIS on the protection channels on the span adjacent to the affected span, until the node receives an indication that the ring switch has been dropped. + +**Rule S-P #3** – If a node that was in the pass-through state due to a SF-R or FS-R request on the ring, and the node is now sourcing a SF-R or FS-R bridge request (due to Rule S-P #2a), the node shall: + +- 1) determine if there is any need for squelching and squelch accordingly; and +- 2) execute the ring bridge and switch. + +**Rule S-P #4** – If a pass-through node receives from at least one direction an APS byte that has itself as the source ID, it shall source Idle in both directions. + +##### **7.2.6.2.5 Transitions between pass-through states** + +This subclause provides the set of rules necessary to change from a K-byte pass-through state to a full pass-through state, and vice versa. + +The following transition rules apply: + +**Rule P-P #1 – TRANSITION FROM K-BYTE PASS-THROUGH TO FULL PASS-THROUGH:** + +- For NEs without extra traffic, a node in K-byte pass-through receives a long-path ring bridge request other than EXER-R not destined to itself, the node shall enter bidirectional full pass-through. +- For NEs with extra traffic, the node shall drop extra traffic bidirectionally, and shall enter unidirectional full pass-through in the direction of the bridge request only. Upon receiving the crossing K-bytes, the node shall enter bidirectional full pass-through. + +**Rule P-P #2 – TRANSITION FROM FULL PASS-THROUGH TO K-BYTE PASS-THROUGH:** A node in bidirectional full pass-through that receives a span bridge request status not destined to itself from both directions shall enter K-byte pass-through. + +### **7.2.7 Examples** + +Appendix I describes how the above-mentioned rules apply in a set of basic examples. + +## **7.3 MS dedicated protection rings** + +This is for further study. + +## **7.4 Linear VC trail protection** + +### **7.4.1 Network architecture** + +LO/HO VC trail protection is a path layer protection mechanism and may be used to protect a trail across an entire operator's network or multiple operators' networks. It is a dedicated end-to-end protection scheme which can be used in different network structures: meshed networks, rings, etc. Protection switching may be either unidirectional or bidirectional. + +Trail protection generically protects against failures in the server layer, and failures and degradations in the client layer. + +The protection scheme can be either 1 + 1, where the dedicated protection trail is only used for protection purposes, or 1:1 where the dedicated protection trail can be used to support extra traffic. Bidirectional protection switching and 1:1 protection switching require an APS protocol to coordinate between the local and remote switch and bridge operations. + +As VC trail 1:1 dedicated protection is a linear protection mechanism, the normal and extra traffic trail termination functions overlap. In a network application this implies that the normal and extra traffic patterns must coincide. As VC trail protection is a dedicated trail protection mechanism, there is no fundamental limitation on the number of NEs within the network connection. + +### 7.4.2 Network objectives + +The following network objectives apply: + +- 1) *Switch time* – The APS algorithm for LO/HO VC trail protection shall operate as fast as possible. A value of 50 ms has been proposed as a target time. Concerns have been expressed over this proposed target time when many VCs are involved. This is for further study. Protection switch completion time excludes the detection time necessary to initiate the protection switch, and the hold-off time. +- 2) *Transmission delay* – The transmission delay depends on the physical length of the trail and the processing functions within the trail. The maximum transmission delay of a dedicated VC protected trail scheme is for further study. Limitations on the transmission delay may be imposed if the target switch completion time for bidirectional protection switching operation is to be met. +- 3) *Hold-off times* – Hold-off times are useful for interworking of protection schemes. The objective is that these times should be provisionable on an individual VC basis. A hold-off timer is started when a defect condition is declared and runs for a non-resettable period which is provisionable from 0 to 10 s in steps of 100 ms. When the timer expires, protection switching is initiated if a defect condition is still present at this point. Note that a defect condition does not have to be present for the entire duration of the hold-off period; only the state at the expiry of the hold-off timer is relevant. Furthermore, the defect that triggers the hold-off timer does not need to be of the same type as the one at the expiry of the hold-off period. +- 4) *Extent of protection* – LO/HO VC trail protection shall restore all traffic which has been interrupted due to a failure of a link connection which has been designated as forming part of a VC trail protection scheme. The traffic terminating at a failed node may be disrupted but traffic passing through to other nodes can survive by switching to the protection trail. +- 5) *Switching types* – Both 1 + 1 and 1:1 trail protection should support unidirectional protection switching, bidirectional protection switching, or both. +- 6) *APS protocol and algorithm* – Both the lower order and higher order VC trail protection APS protocols shall be identical for all network applications. The minimum requirement for the protocol is that it can support 1 + 1 dedicated protection. A 1:1 option to accommodate extra traffic is desirable and is for further study. +- 7) *Operation modes* – 1 + 1 unidirectional protection switching should support revertive switching, non-revertive switching, or both. 1:1 revertive bidirectional protection switching with extra traffic is for further study (It is noted that a principal advantage of a 1:1 architecture is its ability to carry extra traffic). +- 8) *Manual control* – Externally initiated commands may be provided for manual control of protection switching by the operations systems or craft. Externally initiated commands are the same as (or a subset) of those used for linear multiplex section protection. + +- 9) *Switch initiation criteria* – Switch initiation criteria for Signal Fail (SF) and/or Signal Degrade (SD) should be in harmony with definitions used in Recommendation G.783. Switch initiation criteria for VC trail protection should be identical to that for the corresponding SNC/N protection. + +### 7.4.3 Application architecture + +#### 7.4.3.1 Routing + +As a general principle, for each direction of transmission, the protection channels should follow a separate routing from the working channels. + +A node under normal operating conditions is shown in Figure 7-11 a). A bridge is used to simultaneously transmit normal traffic signals onto the working and protection trails. The receiver uses a switch to select the signal from the working trail under normal operating conditions. Figure 7-11 b) shows the node when there is a failure in the working trail. In this case, the receiver will detect the loss of signal and will switch to the protection trail. + + + +a) Normal condition – Transmitted traffic bridged to working and protection paths – Received traffic switch selects working channel + +b) Failure in working channel of incoming traffic – Receiver switch selects protection path + +T1516860-94/d21 + +Figure 7-11/G.841 – Node using 1 + 1 trail or SNC protection. The diagram consists of two parts, (a) and (b), showing a node with 'Working' and 'Protection' paths. In (a), 'Normal condition', traffic enters from the bottom ('Traffic in'), is bridged to both paths, and the receiver switch selects the working path for 'Traffic out'. In (b), 'Failure in working channel of incoming traffic', the working path is broken, and the receiver switch selects the protection path for 'Traffic out'. + +Figure 7-11/G.841 – Node using 1 + 1 trail or SNC protection + +#### 7.4.3.2 1 + 1 unidirectional protection switching + +Unidirectional protection switching is illustrated in Figure 7-12 for a 1 + 1 architecture. It is identical to bidirectional protection switching, except that for unidirectional failures the unaffected direction of transmission is not switched. Consequently, an APS channel is not required to coordinate switching of the unaffected direction of transmission. + +Figure 7-12 a) illustrates a 1 + 1 trail protection network with traffic transmitted between nodes A and B. Traffic inserted at node A is transmitted on different trails in two directions to node B. Under normal operating conditions in revertive modes of operation, the receiver at node B selects the traffic from the working trail. Traffic inserted at node B is also transmitted in two directions to node A. + +When there is a unidirectional failure on the working trail, as shown in Figure 7-12 b), the tail-end switch selects the signal from the protection trail. If a single point failure cuts both directions of transmission, then both directions of transmission on the working trail fail and both directions of transmission switch automatically to the protection trail. + +Traffic can be restored when multiple failures affect traffic on only one of the trails (either working or protection). If both trails are affected by certain failures, then traffic cannot be restored. Traffic terminating at a failed node is disrupted, but traffic passing through to other nodes can survive by switching to the protection trail. + + + +Diagram (a) showing normal conditions of a two-fibre 1+1 trail/SNC protection network. Two nodes, A and B, are connected by two fibres. Node A is at the top and node B is at the bottom. Each node has a switch mechanism. In normal conditions, traffic flows from external sources into the fibres and is received at the opposite node. Solid lines represent the active traffic paths, and dashed lines represent the protection paths. + +a) Normal conditions + + + +Diagram (b) showing a unidirectional failure in Fibre 1. The failure is indicated by an 'X' on the top fibre between the external source and node A. Node B has performed a 'Switch to protection trail', redirecting the traffic that was originally on Fibre 1 to the protection path (dashed line) to reach node A. + +b) Unidirectional failure – Fibre 1 + + + +Diagram (c) showing a unidirectional failure in Fibre 2. The failure is indicated by an 'X' on the bottom fibre between node A and the external destination. Node B has switched its traffic to the protection path (dashed line) to bypass the failure and reach the destination. + +T1516880-94 + +c) Unidirectional failure – Fibre 2 + +**Figure 7-12/G.841 – Two-fibre 1 + 1 trail/SNC protection network with unidirectional protection switching** + +#### 7.4.3.3 1 + 1 bidirectional protection switching + +Figure 7-13 a) illustrates a 1 + 1 trail protection network with traffic transmitted between nodes A and B. Traffic inserted at node A is transmitted on different trails in two directions to node B. Under normal operating conditions in revertive mode of operation, the receiver at node B selects the traffic from the working trail. Traffic inserted at node B is also transmitted in two directions to node A. + +When there is a unidirectional failure on the working trail, as shown in Figure 7-13 b), the tail-end switch selects the signal from the protection trail. For bidirectional protection switching, an indication is sent via the APS protocol to force the unaffected direction of transmission to also switch to the protection trail. If a single point failure cuts both directions of transmission, then both directions of transmission on the working trail fail and both directions of transmission switch automatically to the protection trail. + +Traffic can be restored when multiple failures affect traffic on only one of the trails (either working or protection). If both trails are affected by certain failures, then traffic cannot be restored. Traffic terminating at a failed node is disrupted, but traffic passing through to other nodes can survive by switching to the protection trail. + + + +Diagram (a) showing normal conditions of a two-fibre 1+1 trail/SNC protection network. Two nodes, A and B, are connected by two solid lines (Fibre 1 and Fibre 2) and two dashed lines (protection trails). Clouds represent traffic sources/sinks. Arrows show traffic entering node A from the top, being split onto the two solid lines, and then recombined at node B before exiting at the bottom. Dashed lines show the protection paths. + +a) Normal conditions + + + +Diagram (b) showing a unidirectional failure in Fibre 1. Node A has a switch to the protection trail. Node B has a switch to the protection trail. A cross marks the failure in Fibre 1 between the clouds and node A. Traffic from the top enters node A and is switched to the protection trail. At node B, the traffic is switched back to Fibre 2 and exits at the bottom. + +b) Unidirectional failure – Fibre 1 + + + +Diagram (c) showing a unidirectional failure in Fibre 2. Node A has a switch to the protection trail. Node B has a switch to the protection trail. A cross marks the failure in Fibre 2 between node A and the clouds. Traffic from the top enters node A and is split onto Fibre 1 and the protection trail. At node B, the traffic from Fibre 1 is switched to the protection trail and exits at the bottom. + +c) Unidirectional failure – Fibre 2 + +T1516890-94 + +**Figure 7-13/G.841 – Two-fibre 1 + 1 trail/SNC protection network with bidirectional protection switching** + +#### 7.4.3.4 1:1 protection + +This protection scheme is for further study. + +#### 7.4.3.5 Traffic misconnection + +This is for further study. + +### 7.4.4 Switch initiation criteria + +LO/HO VC trail protection switch requests are automatically initiated based on trail signal fail and trail signal degrade commands (such as AU-AIS and error performance) and APS commands. + +#### 7.4.4.1 1 + 1 unidirectional protection switching + +A request can be: + +- 1) an automatically initiated command (SF or SD) associated with a VC trail; +- 2) a state (Wait-To-Restore, No Request) of the VC trail protection process; or +- 3) an externally initiated command (Clear, Lockout, Forced Switch, Manual Switch). + +For the 1 + 1 architecture, all requests are local. The priority of local requests is given in Table 7-13. + +**Table 7-13/G.841 – Priority of local requests** + +| Local request
(i.e. automatically initiated command, state, or
externally initiated command) | Order of priority | +|-------------------------------------------------------------------------------------------------------------|--------------------------| +| Clear | Highest | +| Lockout of Protection | ↑ | +| Forced Switch | · | +| Signal Fail | · | +| | · | +| Signal Degrade | · | +| Manual Switch | · | +| | · | +| Wait-To-Restore | ↓ | +| No Request | Lowest | + +NOTE 1 – A forced switch to protection should not be overridden by a Signal Fail on the protection channel. Since unidirectional protection switching is being performed and no APS protocol is supported over the protection channel, Signal Fail on the protection channel does not interfere with the ability to perform a forced switch to protection. + +NOTE 2 – The working channel number need not be a part of the switch commands, since a 1 + 1 system has only one working channel and one protection channel. + +##### 7.4.4.1.1 Externally initiated commands + +Externally initiated commands are listed below in the descending order of priority. These commands are applicable for both revertive and non-revertive operation. However, depending on the operation mode, some commands may result in the same action taken. The functionality of each is described below. + +**clear:** This command clears all the externally initiated switch commands listed below and WTR at the node to which the command was addressed. + +NOTE – In the definition of the VC trail protection in the 1995 version of Recommendation G.841, the clear command did not clear WTR. Equipment which was designed according to that 1995 definition will not clear WTR if a clear command is sent to this equipment. However, it is possible to achieve a similar behaviour by a carefully selected sequence of external commands (e.g. manual switch followed by clear). + +**Lockout of Protection (LP):** Prevents the selector from switching to the protection VC trail, by issuing a Lockout of Protection request. + +**Forced Switch to Protection (FS-P):** Switches the selector for normal traffic from the working VC trail to the protection VC trail (unless an equal or higher priority switch request is in effect). + +**Forced Switch to Working (FS-W):** Switches the selector for normal traffic from the protection VC trail to the working VC trail (unless an equal or higher priority switch request is in effect). + +NOTE – The FS-W command is unique only in 1 + 1 non-revertive systems, since the LP command would produce the same effect on a revertive system. Since Forced Switch has higher priority than Signal Fail or Signal Degrade commands on the working VC trail, this command will be carried out regardless of the condition of the working VC trail. + +**Manual Switch to Protection (MS-P):** Switches the selector for normal traffic from the working VC trail to the protection VC trail (unless an equal or higher priority switch request is in effect). + +**Manual Switch to Working (MS-W):** Switches the selector for normal traffic from the protection VC trail to the working VC trail (unless an equal or higher priority switch request is in effect). + +NOTE – The MS-W command is unique only in 1 + 1 non-revertive systems, since the clear command would produce the same result on a revertive system. Since Manual Switch has lower priority than Signal Fail or Signal Degrade on a working VC trail, this command will be carried out only if the working VC trail is not in the Signal Fail or Signal Degrade condition. + +##### 7.4.4.1.2 Automatically initiated commands + +The two automatically initiated commands are Signal Fail and Signal Degrade. + +###### 7.4.4.1.2.1 Higher order automatically initiated commands + +For HO VCs, the Signal Fail automatically initiated command is defined as the presence of the TSFprot condition generated by the higher order Trail Termination function defined in Recommendation G.783. + +For HO VCs, the Signal Degrade automatically initiated command is defined as the presence of the TSD condition generated by the lower order Trail Termination function defined in Recommendation G.783. + +###### 7.4.4.1.2.2 Lower order automatically initiated commands + +For LO VCs, the Signal Fail automatically initiated command is defined as the presence of the TSFprot condition generated by the lower order Trail Termination function defined in Recommendation G.783. + +For LO VCs, the Signal Degrade automatically initiated command is defined as the presence of the TSD condition generated by the lower order Trail Termination function defined in Recommendation G.783. + +#### 7.4.4.2 1 + 1 bidirectional protection switching + +For further study. + +#### 7.4.4.3 1:1 protection switching + +For further study. + +### **7.4.5 Protection switching protocol** + +#### **7.4.5.1 1 + 1 unidirectional protection switching** + +In this architecture, there is no APS channel required. + +#### **7.4.5.2 1 + 1 bidirectional protection switching** + +At the HO VC level, the APS channel can make use of bits 1-4 of byte K3 (formerly byte Z4). At the LO VC level, the APS channel can make use of bits 1-4 of byte K4 (formerly byte Z7). The specific protocol is for further study. + +The APS acceptance process is for further study. + +#### **7.4.5.3 1:1 protection switching** + +This is for further study. + +### **7.4.6 Protection algorithm operation** + +#### **7.4.6.1 1 + 1 unidirectional protection switching** + +##### **7.4.6.1.1 Control of the bridge** + +In the 1 + 1 architecture, normal traffic is permanently bridged to the working and protection channels. + +##### **7.4.6.1.2 Control of the selector** + +In the 1 + 1 architecture in unidirectional protection switching operation, the selector is controlled by the highest priority local condition, state, or externally initiated command. Therefore, each end operates independently of the other. If a condition of equal priority (e.g. SF, SD) exists on both channels, switching shall not be performed (Note that this algorithm makes no distinction between the "severity" of a Signal Degrade, only that a Signal Degrade condition exists). + +For automatically initiated commands, the protection switch completion shall operate as fast as possible. A value of 50 ms has been proposed as a target time. Concerns have been expressed over this proposed target time when many trails are involved. This is for further study. Protection switch completion time excludes the detection time necessary to initiate the protection switch and hold-off time. + +###### **7.4.6.1.2.1 Revertive mode** + +In the revertive mode of operation, the normal traffic signal shall be restored, i.e. the normal traffic signal on the protection trail shall be switched back to the working trail when this working trail has recovered from the fault. + +To prevent frequent operation of the selector due to an intermittent fault, a failed working trail must become fault-free. After the failed working trail meets this criterion (and no other externally initiated commands are present), a fixed period of time shall elapse before it is used again to carry the normal traffic signal. This period, called Wait-To-Restore, should be on the order of 5-12 minutes, and should be capable of being set using 1-second steps. During this state, switching does not occur. An SF or SD condition shall override the WTR. After the WTR period is completed, a No Request state is entered. Switching of the normal traffic signal then occurs from the protection channel to the working channel. + +NOTE – This revertive mode could be used to support certain services where the shortest physical route is maintained under non-failure conditions for a bidirectional connection. + +###### 7.4.6.1.2.2 Non-revertive mode + +When the failed trail is no longer in an SD or SF condition, and no other externally initiated commands are present, a No Request state is entered. During this state, switching does not occur. + +#### 7.4.6.2 1 + 1 bidirectional protection switching + +This is for further study. + +#### 7.4.6.3 1:1 protection switching + +This is for further study. + +# 8 SDH subnetwork connection protection + +## 8.1 Network architecture + +SNC/I protection, generically, protects against failures in the server layer. The protection process and the defect detection process are performed by two adjacent layers. The server layer performs the defect detection process, and forwards the status to the client layer by means of the Server Signal Fail (SSF) signal. + +SNC/N protection, generically, protects against failures in the server layer and against failures and degradations in the client layer. + +LO/HO SNC protection is another path layer protection. It is a dedicated protection scheme which can be used in different network structures; meshed networks, rings, etc. + +This is dedicated 1 + 1 or 1:1 protection in which traffic at the transmit end of a subnetwork connection is transmitted two separate ways over working and protection paths. The 1:1 dedicated protection would be able to support extra traffic. + +In the case of 1 + 1 dedicated protection, the transmit end is permanently bridged, where the traffic will be transmitted on both the working and protection subnetwork connections. At the receive end of the SNC, a protection switch is effected by selecting one of the signals based on purely local information. No APS protocol is required for this protection switching scheme if it is unidirectional. + +In the case of bidirectional protection switching, 1:1 protection switching or carriage of extra traffic in the protection trail, an APS protocol is required to coordinate between the local and remote switch and bridge operations. This may require a sub-layering technique, and is for further study. + +## 8.2 Network objectives + +The following network objectives apply: + +- 1) *Switch time* – The algorithm for LO/HO SNC protection shall operate as fast as possible. A value of 50 ms has been proposed as a target time. Concerns have been expressed over this proposed target time when many subnetwork connections are involved. This is for further study. Protection switch completion time excludes the detection time necessary to initiate the protection switch and the hold-off time. +- 2) *Transmission delay* – 1 + 1 unidirectional protection switching does not require transmission of APS signalling, so signalling transmission delays are not present. +- 3) *Hold-off times* – Hold-off times are useful for interworking of protection schemes. The objective is that these times should be provisionable on an individual VC basis. A hold-off timer is started when a defect condition is declared and runs for a non-resettable period which is provisionable from 0 to 10 s in steps of 100 ms. When the timer expires, protection + +switching is initiated if a defect condition is still present at this point. Note that a defect condition does not have to be present for the entire duration of the hold-off period, only the state at the expiry of the hold-off timer is relevant. Furthermore, the defect that triggers the hold-off timer does not need to be of the same type as the one at the expiry of the hold-off period. + +- 4) *Extent of protection* – LO/HO SNC protection shall restore all LO/HO SNC protected traffic (except extra traffic) which has been interrupted due to a failure of a link connection which has been designated as forming part of a SNC protection scheme. +- 5) *Switching types* – 1 + 1 SNC protection should support unidirectional protection switching. Other architectures are for further study. +- 6) *APS protocol and algorithm* – The SNC protection process should operate in a similar manner at both the HO and LO layers. +- 7) *Operation modes* – 1 + 1 unidirectional protection switching should support revertive switching, non-revertive switching, or both. 1:1 bidirectional protection switching with extra traffic is for further study (It is noted that a principal advantage of a 1:1 architecture is its ability to carry extra traffic). +- 8) *Manual control* – Externally initiated commands may be provided for manual control of protection switching by the operations systems or craft. Externally initiated commands are the same as (or a subset of) those used for linear multiplex section protection. +- 9) *Switch initiation criteria* – Switch initiation criteria for Signal Fail (SF) and/or Signal Degrade (SD) based on either BER or block error performance should be in harmony with definitions used in Recommendation G.783. Switch initiation criteria for SNC/N protection should be identical to that for the corresponding VC trail protection. + +## 8.3 Application architecture + +### 8.3.1 Routing + +As a general principle, for each direction of transmission, the protection channels should follow a separate routing from the working channels. + +A node under normal operating conditions is shown in Figure 7-11 a). A bridge is used to simultaneously transmit signals onto the working and protection SNCs. The receiver uses a switch to select the signal from the working SNC under normal operating conditions in revertive mode of operation. Figure 7-11 b) shows the node when there is a failure in the working SNC. In this case, the receiver will detect the loss of signal and will switch automatically to the protection SNC. + +### 8.3.2 1 + 1 unidirectional protection switching + +Figure 7-12 a) illustrates SNC protection with traffic transmitted between nodes A and B. Traffic inserted at Node A is transmitted on different SNCs in separate directions to Node B (e.g. a working SNC and a protection SNC). Under normal operating conditions in revertive mode of operation, the receiver at node B selects the traffic signal on the working SNC. When there is a failure on the working SNC, as shown in Figure 7-12 b), the tail-end switch selects the protection SNC. If there is a failure in the protection SNC, as shown in Figure 7-12 c), then the receiver will not need to switch and will continue to detect traffic from the working SNC. + +### 8.3.3 Other architectures + +1:1 revertive bidirectional protection switching with extra traffic is for further study. + +## 8.4 Switch initiation criteria + +### 8.4.1 1 + 1 unidirectional protection switching + +A request can be: + +- 1) an automatically initiated command (SF or SD) associated with a VC subnetwork connection; +- 2) a state (Wait-To-Restore, No Request) of the SNC protection process; or +- 3) an externally initiated command (Clear, Lockout, Forced Switch, Manual Switch). + +For the 1 + 1 architecture, all requests are local. The priority of local requests is given in Table 8-1. + +**Table 8-1/G.841 – Priority of local requests** + +| Local request
(i.e. automatically initiated command, state, or
externally initiated command) | Order of priority | +|-------------------------------------------------------------------------------------------------------------|--------------------------| +| Clear | Highest | +| Lockout of Protection | ↑ | +| Forced Switch | · | +| Signal Fail | · | +| | · | +| Signal Degrade | · | +| Manual Switch | · | +| | · | +| Wait-To-Restore | ↓ | +| No Request | Lowest | + +NOTE 1 – A forced switch to protection should not be overridden by a Signal Fail on the protection channel. Since unidirectional protection switching is being performed and no APS protocol is supported over the protection channel, Signal Fail on the protection channel does not interfere with the ability to perform a forced switch to protection. + +NOTE 2 – The working channel number need not be a part of the switch commands, since a 1 + 1 system has only one working and one protection channel. + +#### 8.4.1.1 Externally initiated commands + +Externally initiated commands are listed below in the descending order of priority. These commands are applicable for both revertive and non-revertive operation. However, depending on the operation mode, some commands may result in the same action taken. The functionality of each is described below. + +**clear:** This command clears all of the externally initiated switch commands listed below and WTR at the node to which the command was addressed. + +NOTE – In the definition of the SNC protection in the 1995 version of Recommendation G.841, the clear command did not clear WTR. Equipment which was designed according to that 1995 definition will not clear WTR if a clear command is sent to this equipment. However, it is possible to achieve a similarly behaviour by a carefully selected sequence of external commands (e.g. manual switch followed by clear). + +**Lockout of Protection (LP):** Prevents the selector from switching to the protection VC subnetwork connection, by issuing a Lockout of Protection request. + +**Forced Switch to Protection (FS-P):** Switches the selector from the working VC subnetwork connection to the protection VC subnetwork connection (unless an equal or higher priority switch request is in effect). + +**Forced Switch to Working (FS-W):** Switches the selector from the protection VC subnetwork connection to the working VC subnetwork connection (unless an equal or higher priority switch request is in effect). + +NOTE – The FS-W command is unique only in 1 + 1 non-revertive systems, since the LP command would produce the same effect on a revertive system. Since Forced Switch has higher priority than Signal Fail or Signal Degrade commands on the working VC subnetwork connection, this command will be carried out regardless of the condition of the working VC subnetwork connection. + +**Manual Switch to Protection (MS-P):** Switches the selector from the working VC subnetwork connection to the protection VC subnetwork connection (unless an equal or higher priority switch request is in effect). + +**Manual Switch to Working (MS-W):** Switches the selector from the protection VC subnetwork connection to the working VC subnetwork connection (unless an equal or higher priority switch request is in effect). + +NOTE – The MS-W command is unique only in 1 + 1 non-revertive systems, since the clear command would produce the same effect on a revertive system. Since Manual Switch has lower priority than Signal Fail or Signal Degrade on a working VC subnetwork connection, this command will be carried out only if the working VC subnetwork connection is not in the Signal Fail or Signal Degrade automatically initiated command. + +#### 8.4.1.2 Automatically initiated commands + +The two automatically initiated commands are Signal Fail and Signal Degrade. + +##### 8.4.1.2.1 Higher order automatically initiated commands + +For HO VCs, the Signal Fail automatically initiated command is defined as the presence of: + +- For SNC/I, the SSF condition generated by the Server to the higher order Path Adaptation function (e.g. MS/Sn adaptation defined in Recommendation G.783); +- For SNC/N, the TSFprot condition generated by the higher order Path Termination function defined in Recommendation G.783. + +For HO VCs, using SNC/N, the Signal Degrade automatically initiated command is defined as the presence of the TSD condition generated by the higher order Path Termination function defined in Recommendation G.783. + +##### 8.4.1.2.2 Lower order automatically initiated commands + +For LO VCs, the Signal Fail automatically initiated command is defined as the presence of: + +- for SNC/I, the SSF condition generated by the Server to the lower order Path Adaptation function (e.g. Sn/Sm adaptation defined in Recommendation G.783); +- for SNC/N, the TSFprot condition generated by the lower order Path Termination function defined in Recommendation G.783. + +For LO VCs using SNC/N, the Signal Degrade automatically initiated command is defined as the presence of the TSD condition generated by the lower order Path Termination function defined in Recommendation G.783. + +### 8.4.2 Other architectures + +For further study. + +## **8.5 Protection switching protocol** + +### **8.5.1 1 + 1 unidirectional protection switching** + +In this architecture, there is no APS channel required. + +### **8.5.2 Other architectures** + +For further study. + +## **8.6 Protection algorithm operation** + +### **8.6.1 1 + 1 unidirectional protection switching algorithm** + +#### **8.6.1.1 Control of the bridge** + +In the 1 + 1 architecture, the normal traffic signal is permanently bridged to working and protection. + +#### **8.6.1.2 Control of the selector** + +In the 1 + 1 architecture in unidirectional protection switching operation, the selector is controlled by the highest priority local condition, state, or externally initiated command. Therefore, each end operates independently of the other. If a condition of equal priority (e.g. SF, SD) exists on both channels, switching shall not be performed (Note that this algorithm makes no distinction between the "severity" of a Signal Degrade, only that a Signal Degrade condition exists). + +For automatically initiated commands, the protection switch completion shall operate as fast as possible. A value of 50 ms has been proposed as a target time. Concerns have been expressed over this proposed target time when many subnetwork connections are involved. This is for further study. Protection switch completion time excludes the detection time necessary to initiate the protection switch, and hold-off time. + +##### **8.6.1.2.1 Revertive mode** + +In the revertive mode of operation, the normal traffic signal shall be restored, i.e. the signal on the protection subnetwork connection shall be switched back to the working subnetwork connection when this working subnetwork connection has recovered from the fault. + +To prevent frequent operation of the selector due to an intermittent fault, a failed subnetwork connection must become fault-free. After the failed working subnetwork connection meets this criterion, (and no other externally initiated commands are present) a fixed period of time shall elapse before the normal traffic signal is restored to that subnetwork connection. This period, called Wait-To-Restore, should be on the order of 5-12 minutes, and should be capable of being set using 1-second steps. During this state, switching does not occur. An SF or SD automatically initiated command shall override the WTR. After the WTR period is completed, a No Request state is entered. Switching then occurs from the protection channel to the working channel. + +NOTE – This revertive mode could be used to support certain services where the shortest physical route is maintained under non-failure conditions for a bidirectional connection. + +##### **8.6.1.2.2 Non-revertive mode** + +When the failed SNC is no longer in an SD or SF condition, and no other externally initiated commands are present, a No Request state is entered. During this state, switching does not occur. + +### **8.6.2 Other architectures** + +For further study. + +# **MS shared protection rings (transoceanic application)** + +## **A.1 Application** + +Because of the unique character of transoceanic systems, i.e. very long transmission paths, the approach described for general purpose MS shared protection rings is insufficient. For some types of failures, a total adaptation of the general purpose MS shared protection ring would lead to restoration transmission paths that would cross the ocean three times. The inherent delays in such an approach will only result in degraded performance. + +Therefore, additional text for implementing the "transoceanic application" option demonstrates that using the existing protocol and augmenting the switching action at the ring nodes results in eliminating the problem mentioned above. It should be noted that these problems will only manifest themselves in long-haul networks, where the distances between the nodes on the ring exceed 1500 km. While this annex was developed to meet the needs of the transoceanic application, the protocol modifications in this annex can be used to meet the needs of other high delay spans within an MS shared protection ring, such as those being transmitted over satellite systems. + +When a ring switch occurs on the transoceanic ring network, all AU-4 tributaries affected by the failure are bridged at their source nodes onto the protection channels that travel away from the failure. When the affected tributaries reach their final destination nodes, they are switched to their original drop points. This is illustrated in Figure A.1. This is accomplished by using the local node ring maps and the K-byte protocol. The differences in Figures 6-2 and A.1 illustrate the differences in the length of the protection channel. + +For the non-transoceanic ring network, the extra traffic remains off the ring network until the failure is cleared. Since only the affected AU-4 tributaries are switched for the transoceanic ring network, the pre-empted extra traffic can be re-established on the protection channels not used to restore the normal traffic. The signalling channel used to re-establish the extra traffic is the DCC. + +## **A.2 Network objectives** + +For transoceanic applications of MS shared protection rings, some additional network objectives apply: + +- 1) *Switch time* – The switch completion time shall be less than 300 ms, independent of whether the ring is carrying extra traffic. This supersedes objective 1) of 7.2.2. +- 2) *Extent of protection* – Objective 4 b) of 7.2.2 is superseded by the following: b) The ring shall restore all traffic possible, even under conditions of multiple bridge requests of the same priority. +- 3) *APS protocol and algorithm* + - a) AUG squelching is not required. This supersedes objective 6 j) of 7.2.2. + - b) During a failure, pre-empted extra traffic can be re-established on the protection channels not used to restore the normal traffic. + - c) For transoceanic applications, ring maps are used to switch traffic affected by a failure at intermediate nodes. A mechanism should be accommodated that auto-provisions the data required for these maps, and maintains its consistency. The mechanism proposed for use is the DCC. + +- d) Objective 6 i) of 7.2.2 is superseded by the following: i) If a ring switch exists and a failure of equal priority occurs on another span requiring a ring switch, then, if the priority of the bridge request is Signal Fail (Ring) or higher, both ring switches shall be established resulting in the ring segmenting into two separate segments. + +## A.3 Application architecture + +An MS shared protection ring in a transoceanic application uses SDH multiplex section layer indications to trigger the protection switching. Switching action is performed only on AU-4 tributaries affected by the failure. Multiplex section indicators include MS failure conditions, and signalling messages that are sent between nodes to affect a coordinated MS protection switch. + +In the event of a failure, ring switches are established at any node whose traffic is affected by the failure. Unlike the general purpose approaches described earlier, no loopbacks are established. Loopbacks and switching only at the nodes adjacent to a failure are the cause of triple ocean crossing encountered by the traffic restoration path mentioned above. Therefore, in the transoceanic approach, all nodes are allowed to switch and use the existing protocol in conjunction with ring maps. As in the general purpose cases described in 7.2.1.1 and 7.2.1.2, the affected traffic is rerouted away from the failure over the protection channels. + +The problem of misconnection is eliminated for the transoceanic ring application because there are no loopbacks at the switching nodes. It is the looping at switching nodes that sets up the potential for misconnections. As a consequence, the "squelching" described for general purpose MS shared protection rings is not necessary. Additionally, single and multiple failures resulting in ring switching are executed in the same manner, by simply bridging and switching and taking advantage of the ring map information just described. + +## A.4 Switching criteria + +The criteria found in 7.2.4 applies, with the following additional interpretations. + +**forced switch to protection - ring (FS-R):** This command performs the ring switch of normal traffic signals from working channels to the protection channels for the span between the node at which the command is initiated and the adjacent node to which the command is destined. This switch occurs regardless of the state of the protection channels, unless the protection channels are satisfying a higher priority bridge request, or a signal failure (or a K-byte failure) exists on the long-path protection channels. For transoceanic applications, the FS-R is meant to prompt the same switching response as that for a cable cut on the span between the node at which the command is initiated and the adjacent node to which the command is destined. As in the behaviour for cable cuts, however, no loopbacks are established. Normal traffic between any two nodes that had been using the affected span is now rerouted away from this span via the protection channels. + +**manual switch to protection - ring (MS-R):** For transoceanic applications, the note under the FS-R description also applies here. + +**exercise - ring (EXER-R):** For transoceanic applications, no extra traffic is affected either. + +**exercise - span (EXER-S):** For transoceanic applications, no extra traffic is affected either. + +As described in 7.4.2, the SF bridge request is used to protect normal traffic affected by a hard failure, while the SD bridge request is used to protect against a soft failure. The bridge requests are transmitted on both the short and long paths. Each intermediate node verifies the destination node ID of the long-path bridge request and relays the bridge request. The destination node receives the bridge request, performs the activity according to the priority level, and sends the Bridged indication. + +For transoceanic applications, this activity occurs at both the switching nodes and the intermediate nodes. + +As described also in 7.4.2, the WTR bridge request is used to prevent frequent oscillation between the protection channels and the working channels. The intent is to minimize oscillations, since hits are incurred during switching. The WTR bridge request is issued after the working channels' BER meets the restoral threshold. The WTR is issued only after an SF or an SD condition and, thus, does not apply for externally initiated bridge requests. For ring switches in a transoceanic application, a WTR bridge request received bidirectionally by an intermediate node with bridged and switched traffic results in the following. The intermediate node initiates a local WTR whose time interval is one half that of the switching node WTR interval. For transoceanic applications, the WTR interval is set to the same value at all nodes. + +## **A.5 Protection switch protocol** + +The protocol is the same as described in 7.2.5. + +## **A.6 Protection algorithm operation** + +For transoceanic applications, the pass-through state at intermediate nodes may also involve switching activity when ring switches are required, as described below. + +In transoceanic applications, intermediate nodes may engage in some switching activity. As described in 6.2, all nodes are allowed to switch if their added/dropped traffic is affected by a failure. This includes intermediate nodes. When a ring switch is required, any intermediate node shall execute bridges and switches if its added/dropped traffic is affected by the failure. The determination of affected traffic is made by examining the K1 bridge requests (which indicate the nodes adjacent to the failure or failures) and the stored ring maps (which indicate the relative position of the failure and the added/dropped traffic destined toward that failure). Only those AU-4 tributaries affected by the failure are bridged and switched, using the same rules as described in this Recommendation. Specific details of the bridging and switching at intermediate nodes are given in the figures of the examples shown in Appendix I. + +The following rules modify or extend those found in 7.2.6 in order to satisfy the needs of the transoceanic application. + +**Rule Basic #3 – K2 BITS 6-8 UPDATE:** Given that "All bridge and switch actions shall be reflected by updating byte K2 bits 6-8, unless an MS-RDI condition exists," for transoceanic applications, this only occurs at switching nodes. The rest of this rule applies as stated in 7.2.6.2. + +**Rule Basic #4:** For transoceanic applications, the following supersedes Rule Basic #4: Bridge requests (due to a locally detected failure, an externally initiated command, or received K-bytes) shall pre-empt bridge requests in the prioritized order given in Table 7-1. Bridge requests shall pre-empt bridge request status signalling regardless of the priority of each. Bridge request status signalling shall never pre-empt a bridge request. + +**Rule I-S #1b:** Since transoceanic applications do not require squelching, the squelching activities described in this rule are not taken. + +**Rule S-S #1a:** Since transoceanic applications do not require squelching, the squelching activities described in this rule are not taken. For transoceanic applications only, the following supersedes Rule S-S #1a: + +- 1) Coexistence of FS-R with SF-R does not apply to transoceanic applications. +- 2) When a ring switching node receives the new ring bridge request with an 'Idle' status code, it shall either: + - a) maintain the Bridge and Switch (and drop the extra traffic, which is re-established if applicable), and change the status code to 'Idle' for both sides, if the node had been sending 'Bridged and Switched'; or + - b) change the status code to 'Bridged and Switched' for both sides, if the node had been sending 'Idle'. +- 3) When the node which executes 2) receives the ring bridge request with a 'Bridged and Switched' status code, it changes the status code to 'Bridged and Switched' for both sides, if the node had been sending 'Idle'. + +**Rule S-S #1b:** Since transoceanic applications do not require squelching, the squelching activities described in this rule are not taken. For transoceanic applications only, the following supersedes Rule S-S #1b: + +- 1) Coexistence of FS-R with SF-R does not apply to transoceanic applications. +- 2) When a ring switching node receives the new ring bridge request with an 'Idle' status code, it shall either: + - a) maintain the Bridge and Switch (and drop the extra traffic, which is re-established if applicable), and change the status code to 'Idle' for both sides, if the node had been sending 'Bridged and Switched'; or + - b) change the status code to 'Bridged and Switched' for both sides, if the node had been sending 'Idle'. +- 3) When the node which executes 2) receives the ring bridge request with a 'Bridged' status code, it shall either: + - a) change the status code to 'Bridged' for the long-path side, if the node had been sending 'Idle'; or + - b) change the status code to 'Bridged and Switched' for both sides, if the node had been sending 'Bridged'. +- 4) When the node which executes 3) receives the ring bridge request with a 'Bridged and Switched' status code, it changes the status code to 'Bridged and Switched' for both sides, if the node had been sending 'Bridged'. + +**Rule S #4a:** For the FS-R with FS-R coexisting switches, and the SF-R and SF-R coexisting switches, the ring does not split into multiple subrings. For the transoceanic application of MS shared protection rings, the ring switching used for transoceanic systems does not require looping traffic at switching nodes. Consequently, the ring is segmented, but not into smaller rings. The segmentation is into separate linear add/drop chains separated by cable failures and/or the number of forced switches (ring) existing on the ring. Coexistence of FS-R with SF-R does not apply to transoceanic applications. + +**Rule S-P #2c:** This rule is not required for transoceanic applications. + +**Rule S #1d:** For transoceanic applications, the following supersedes Rule S #1d: Whenever a node detects an incoming failure on the working and on the protection channels, it shall always source over the short path a short-path ring bridge request, even in the case of multiple failures, as long as + +the ring bridge request is not pre-empted by a higher priority bridge request which is located on the same span [See Figure 7-10 b)]. This rule takes precedence over Rule S #1c. Note that whenever a node receives in one direction a ring bridge request on the short path (indicating that the signal it is sending has failed), and detects on the other side an incoming failure on the working and on the protection channels, it shall signal the detected failure over both the short and the long paths [see Figure 7-10 c)]. + +**Rule S-S #2d:** For transoceanic applications, the following supersedes Rule S-S #2d: If a bridge request (due to a locally detected failure, an externally initiated command, or received K-bytes) over a different span pre-empts an SF-R bridge request, the switching node sourcing the SF-R bridge request shall continue signalling its bridge request, shall drop its bridge and switch, and shall insert AU-AIS over the failed tributaries. + +**Rule S-P #1e:** For transoceanic applications, the following supersedes Rule S-P #1e: When a node that is currently executing a ring switch receives a ring bridge request for a non-adjacent span of greater priority than the ring switch it is executing, it shall either: + +- 1) maintain ring bridges and switches on the tributaries affected by the first failure, if the long-path ring bridge request is still signalling that failure; or +- 2) drop ring bridges and switches on the tributaries affected by the first failure, if the long-path ring bridge request is not still signalling that failure. It then enters full pass-through. + +**Rule S-P #1f:** For transoceanic applications, the following supersedes Rule S-P #1f: When a node that is currently executing a ring switch has as its highest priority input long-path ring bridge requests not destined to itself from both directions, it shall either: + +- 1) maintain ring bridges and switches on the tributaries affected by the first failure, if the long path ring bridge requests are still signalling that failure; or +- 2) drop ring bridges and switches on the tributaries affected by the first failure, if the long-path ring bridge requests are not still signalling that failure. It then enters full pass-through. + +**Rule S-P #1g:** For transoceanic applications, this rule does not apply. + +**Rule S-P #2a:** For transoceanic applications, the following supersedes Rule S-P #2a: The transition of a node from full pass-through to switching shall be triggered by: + +- 1) an equal or higher priority externally initiated command; +- 2) the detection of an equal or higher priority failure; +- 3) the receipt of an equal or higher priority bridge request destined to that NE; +- 4) the detection of an SF-R condition (even if lower priority); or +- 5) the receipt of an SF-R bridge request destined to that NE. + +**Rule S-P #3:** For transoceanic applications, the following supersedes Rule S-P #3: If a node that was in the pass-through state due to a SF-R or FS-R bridge request is now sourcing a SF-R or FS-R request (due to Rule S-P #2a), the node shall drop extra traffic and maintain the first failure's ring bridge and switch. + + + +Diagram of a ring switch network in normal state. Six nodes (A, B, C, D, E, F) are arranged in a ring. Node A is at the top left, B is top middle, C is top right. Node F is bottom left, E is bottom middle, D is bottom right. Each node is connected to two adjacent nodes by a pair of lines: a thick grey line (Working) and a thin white line (Protection). Circuit Q is shown entering Node A from the top and exiting Node D at the bottom right. In the normal state, the circuit uses the working lines for the entire path around the ring. + +a) Normal state + + + +Diagram of the same ring switch network in a failed state. The working line between Node B and Node C is broken, indicated by a large 'X'. Node A has a switch that can divert the circuit from the working line to the protection line. Node D has a switch that can divert the circuit from the protection line back to the working line. In the failed state, the circuit is rerouted: it enters Node A, switches to the protection line, travels counter-clockwise through Node F, E, and D, and then switches back to the working line at Node D to continue towards Node C. + +b) Failed state + +T1516920-94/d27 + + + +Working + Protection + Circuit transporting service + +Thick grey rectangle Thin white rectangle Double-headed arrow + +**Figure A.1/G.841 – Example of circuit routing in failure state for a ring switch (transoceanic application)** + +# Multiplex section protection (MSP) 1 + 1 optimized protocol, commands and operation + +## B.1 1 + 1 bidirectional switching optimized for a network using predominantly 1 + 1 bidirectional switching + +This algorithm uses working sections 1 and 2 in order to realize high-speed 1 + 1 non-revertive protection switching. In other words, revertive action is prevented by switching between working sections. + +Bytes K1 and K2 (b1-b5) are exchanged to complete a switch. Since the bridge is permanent (see Figure B.1), the traffic is always bridged to working section 1 and working section 2. Byte K2 indicates the number of the section which carries traffic when no switch is active. This will be referred to as the primary section. The other working section, referred to as the secondary section, provides protection for the primary section. Exchange of K1/K2 to control this protection occurs over the secondary section. The section number on byte K2 will be changed after a switch has cleared. Clearing of a switch is completed when both the receive end switches select the other working section as primary and receive no request. + +In 1 + 1 bidirectional optimized switching, both sections 1 and 2 are equal to working sections. K1/K2 bytes are received on the secondary section. K1/K2 bytes need not always be received on the primary section, but in general, K1/K2 must be sent on both sections to provide for successful clearing operations and to allow recovery of the primary channel mismatch condition (See B.1.5). + +In 1 + 1 bidirectional operation optimized for a network using predominately 1 + 1 bidirectional switching, the selector is on the primary section in the absence of a switch request. All switch requests are for a switch from the primary section to the secondary section. Once a switch request clears normally, traffic is maintained on the section to which it was switched by making that section the primary section. + + + +Diagram of an MSP Switch for 1 + 1 bidirectional switching. On the left, 'Working channel 1' is shown with an arrow pointing left. A 'Permanent bridge' is a vertical line connecting the input to two horizontal lines on the right. The top horizontal line is 'Working section 1 (primary)' with an arrow pointing right. The bottom horizontal line is 'Working section 2 (secondary)' with an arrow pointing right. A 'Selector' is a switch mechanism between the bridge and the sections. It has two positions: '1' (primary) and '2' (secondary). The switch is shown in the 'released position' (position 1), connecting the bridge to Working section 1. A dashed vertical line separates the bridge from the selector. The label 'T1526470-97' is at the bottom right. + +**Figure B.1/G.841 – MSP Switch – 1 + 1 bidirectional switching, optimized (shown in released position with working section 1 as primary)** + +### B.1.1 Lockout + +In 1 + 1 bidirectional optimized switching, Lockout is considered as a local request which is not signalled across the K-bytes. The effect of lockout is to freeze the selector position and transmitted K-bytes until the lockout request is cleared. When a lockout request is cleared, the selector and transmitted K-bytes will be set by applying any changed section conditions and incoming K-bytes to the previous state. + +### B.1.2 Secondary section failure + +The secondary section is considered failed whenever it is an SF or SD condition. As an option, the secondary section may also be considered failed whenever MS-RDI is being received for the secondary section. + +No switch request will be issued or acknowledged when the secondary section has failed. When the secondary section has failed, the near end will always indicate no request on the K1 byte and the selector will choose service from the primary section. In addition, if the secondary section fails while a switch request is active and not locked, the switch request will be abandoned: That is, the selector will be returned to the primary section and no request will be sent on the K1 byte. + +### B.1.3 K1/K2 byte coding + +The K1 byte indicates a request for switch action. + +Bits 1-4 indicate the type of request, as listed in Table B.1. A request can be: + +- 1) a condition (SF or SD) associated with the primary condition. Conditions are not indicated for the secondary section. +- 2) a state (wait-to-restore, no request, reverse request) of the MSP function. Wait-to-restore and reverse request always indicate the primary section. No request always indicates the null signal. +- 3) an external request (forced switch) to switch from the primary to the secondary line. + +**Table B.1/G.841 – Types of request** + +| Bits | Condition, state or external request | Order | +|---------|--------------------------------------|---------| +| 1 2 3 4 | | | +| 1 1 1 1 | Unused (Note 1) | – | +| 1 1 1 0 | Forced switch | Highest | +| 1 1 0 1 | Unused (Note 1) | ↑ | +| 1 1 0 0 | Signal fail | . | +| 1 0 1 1 | Unused (Note 1) | . | +| 1 0 1 0 | Signal degrade | . | +| 1 0 0 1 | Unused (Note 1) | . | +| 1 0 0 0 | Unused (Note 1) | . | +| 0 1 1 1 | Unused (Note 1) | . | +| 0 1 1 0 | Wait-to restore | . | +| 0 1 0 1 | Unused (Note 1) | . | +| 0 1 0 0 | Unused (Note 1) | . | +| 0 0 1 1 | Unused (Note 1) | . | +| 0 0 1 0 | Reverse request | . | +| | | . | +| 0 0 0 1 | Unused (Note 1) | ↓ | +| 0 0 0 0 | No request | Lowest | + +NOTE 1 – When receiving an unused code, the equipment shall behave as though it is still receiving the most recently received used code. + +NOTE 2 – In the case of Signal Degrade (SD) on both working sections, no protection switching should take place. Depending on the order in time of the individual SD, the selectors may be switched to section 1 or section 2. In any case, no switching should take place. + +Bits 5-8 indicate the number of the section to be protected by the switch. This will be the null signal for no request, and the primary section for all other requests. + +**Table B.2/G.841 – K1 channel number** + +| Channel number | Requesting switch action | +|-----------------------|--------------------------------------------------------------------------------| +| 0 | No working section (no request only) | +| 1 | Working section 1
Indicates a request to switch away from section number 1. | +| 2 | Working section 2
Indicates a request to switch away from section number 2. | + +### **B.1.4 K2 byte coding** + +For 1 + 1 bidirectional switching optimized for a network using predominantly 1 + 1 bidirectional switching, the sent K2 byte shall indicate the selector position in bits 1-4: + +- a) Channel number 1 (0001) if section 1 is working; +- b) Channel number 2 (0010) if section 2 is working. + +**Table B.3/G.841 – K2 channel number** + +| Channel number | Indication | +|-----------------------|----------------------| +| 1 | Section 1 is primary | +| 2 | Section 2 is primary | + +### **B.1.5 Primary section mismatch** + +In the event that the near end and far end disagree about which section is primary (i.e. one end is indicating section 1 in byte K2 and the other is indicating section 2), the side that believed section 2 was primary shall change so that section 1 is primary and set its state according to local line conditions and the incoming K-bytes. + +## **B.2 Switch commands** + +### **Forced Switch** + +Transfers service to the secondary section, unless a local Lockout is in effect, an equal or higher priority request is in effect, or the secondary section has failed. Since forced switch has higher priority than SF or SD, Forced Switch will be indicated as the reason for the switch to the secondary section even if the primary section is in an SF or SD condition. + +### **Forced Switch Clear** + +If no lockout is in effect and a forced switch is active, the switch will be cleared by changing the primary line indication to the currently active line and changing the request to no request. If no Forced switch is active, the Forced Switch Clear command is invalid. + +## B.3 Switch operation + +Table B.4 illustrates the operation of a 1 + 1 bidirectional protection switching system for signal failure on the primary section when section 1 is primary. Table B.5 illustrates the operation of a 1 + 1 bidirectional optimized protection switching system for a Forced Switch from the primary to the secondary section when section 2 is primary. Note that for a Forced switch command, the wait to restore state is not necessary for clearing. + +**Table B.4/G.841 – Example of 1 + 1 bidirectional switching optimized for a network using predominantly 1 + 1 bidirectional switching – SF on working section 1** + +| Failure condition or controller state | APS bytes | | | | Action | | +|------------------------------------------------------------------|-----------|-----------|-----------|-----------|----------------------------------------------|--------------------------------------------------------------------| +| | C → A | | A → C | | | | +| | Byte K1 | Byte K2 | Byte K1 | Byte K2 | At C | At A | +| No fault condition traffic on channel 1 | 0000 0000 | 0001 0000 | 0000 0000 | 0001 0000 | | | +| Signal fail on section 1 at side C | 1100 0001 | 0001 0000 | 0000 0000 | 0001 0000 | Detect local request. Update K1. | | +| | 1100 0001 | 0001 0000 | 0010 0001 | 0001 0000 | | Detect remote request. Switch to channel 2. Issue Reverse Request. | +| | 1100 0001 | 0001 0000 | 0010 0001 | 0001 0000 | Detect reverse request. Switch to channel 2. | | +| Signal fail on section 1 at side C cleared and persistence check | 0110 0001 | 0001 0000 | 0010 0001 | 0001 0000 | Issue Wait-to-Restore Request. | | +| Wait to restore expires | 0000 0000 | 0010 0000 | 0010 0001 | 0001 0000 | Send no request. Update K1, K2. | | +| No fault condition. Traffic on section 2 | 0000 0000 | 0010 0000 | 0000 0000 | 0010 0000 | | Send no request. Update K1, K2. | + +**Table B.5/G.841 – Example of 1 + 1 bidirectional switching optimized for a network using predominantly 1 + 1 bidirectional switching – Forced Switch from Working Section 2** + +| Failure condition or controller state | APS bytes | | | | Action | | +|-----------------------------------------|-----------|-----------|-----------|-----------|----------------------------------------------|--------------------------------------------------------------------| +| | C → A | | A → C | | | | +| | Byte K1 | Byte K2 | Byte K1 | Byte K2 | At C | At A | +| No fault condition traffic on channel 2 | 0000 0000 | 0010 0000 | 0000 0000 | 0010 0000 | | | +| Forced Switch from section 2 at side C | 1110 0010 | 0010 0000 | 0000 0000 | 0010 0000 | Detect local request. Update K1. | | +| | 1110 0010 | 0010 0000 | 0010 0010 | 0010 0000 | | Detect remote request. Switch to channel 2. Issue Reverse Request. | +| | 1110 0010 | 0010 0000 | 0010 0010 | 0010 0000 | Detect reverse request. Switch to channel 2. | | +| Clear Forced Switch at side C | 0000 0000 | 0001 0000 | 0010 0010 | 0010 0000 | Send no request. Update K1, K2. | | +| No Switch active. Traffic on section 1. | 0000 0000 | 0001 0000 | 0000 0000 | 0001 0000 | | Send no request. Update K1, K2. | + +# APPENDIX I + +## Examples of protection switching in an MS shared protection ring + +This appendix provides examples showing how the state transition rules are used to execute a ring switch. + +## I.1 Unidirectional signal fail (span) in a four-fibre ring + +See Figure I.1. + +In this example, a span switch is executed and cleared for an SF condition over the working channels in a four-fibre ring. The initial state of the ring is the idle state. At time T1, node F detects an SF condition on its working channels. It becomes a switching node (Rule I-S #1) and sends bridge requests in both directions (Rule S #1). Node G, and all successive intermediate nodes on the long path, enter K-byte pass-through (Rule I-P #1). Node E, upon reception of the bridge request from Node F on the short path, executes a span bridge and transmits an SF span bridge request on the long path, and a Reverse Request on the short path (Rules S #3, S #1, and I-S #1b). Node F, upon reception of the bridge acknowledgment from node E on the short path, executes a span bridge and switch, and updates its K-byte signalling (Rule I-S #1b). Node E, upon reception of the bridge and switch acknowledgment from node F on the short path, completes the switch. Signalling reaches steady-state. + +For transoceanic applications, the switching activities that would take place at the intermediate nodes. On all AU-4 protection channels not being used to protect working channels, extra traffic is restored using the DCC. + +At time $T_2$ , the span SF condition clears, and node F enters the Wait-To-Restore state, and signals its new state in both directions (Rule S-S #3a). Node E, upon reception of the WTR bridge request from node F on the short path, sends out Reverse Request on the short path and WTR on the long path (Rule S-S #3b.) At time $T_3$ , the WTR interval expires. Node F drops the span switch, and sends out No Request codes (Rule I-S #2.) Node E, upon reception of the No Request code from node F on the short path, drops its bridge and switch, and sources the Idle code (Rule I-S #2). Node F, upon reception of the Idle code on the short path, drops its bridge and also sources the Idle code. All nodes then cascade back to idle state. + +## I.2 Unidirectional signal fail (ring) + +See Figure I.2. + +This example covers the case of a unidirectional SF condition in a two-fibre ring, and of a unidirectional SF condition on both working and protection channels in a four-fibre ring. + +The initial state of the ring is the idle state. At time $T_1$ , node F detects an SF condition on its working and protection channels. It becomes a switching node (Rule I-S #1) and sends bridge requests in both directions (Rule S #1). Node G, and all successive intermediate nodes on the long path, enter full pass-through (Rule I-P #1). Node E, upon reception of the bridge request from node F on the short path, transmits an SF ring bridge request on the long path, and a Reverse Request on the short path (Rules S #3, and I-S #1a). Node E, upon reception of the bridge request from node F on the long path, executes a ring bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Node F, upon reception of the acknowledgment from node E on the long path, executes a ring bridge and switch, and updates its K-byte signalling (Rule I-S #1b). Signalling reaches steady-state. + +For transoceanic applications, the switching activities that would take place at the intermediate nodes. On all AU-4 protection channels not being used to protect working channels, extra traffic is restored using the DCC. + +At time $T_2$ , the ring SF condition clears, and node F enters the Wait-To-Restore state, and signals its new state in both directions (Rule S-S #3a). Node E, upon reception of the WTR bridge request from node F on the short path, sends out Reverse Request on the short path and WTR on the long path (Rule S-S #3b). At time $T_3$ , the WTR interval expires. Node F drops the ring switch, and sends out No Request codes (Rule I-S #2). Node E, upon reception of the No Request code from node F on the long path, drops its bridge and switch, and sources the Idle code (Rule I-S #2). Node F, upon reception of the Idle code on the long path, drops its bridge and also sources the Idle code. All nodes then cascade back to the idle state. + +## I.3 Bidirectional signal fail (ring) + +See Figure I.3. + +This example covers the case of a bidirectional SF condition in a two-fibre ring, and of a bidirectional SF condition on both working and protection channels in a four-fibre ring. + +The initial state of the ring is the idle state. At time $T_1$ , nodes E and F detect an SF condition on their working and protection channels. They become switching nodes (Rule I-S #1) and send bridge requests in both directions (Rule S #1). Nodes D and G, and all successive intermediate nodes on the long path, enter full pass-through (Rule I-P #1). Node E, upon reception of the bridge request from node F on the long path, executes a ring bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Node F, upon reception of the bridge request from node E on the long path, executes a ring bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Signalling reaches steady-state. + +For transoceanic applications, the switching activities that would take place at the intermediate nodes. On all AU-4 protection channels not being used to protect working channels, extra traffic is restored using the DCC. + +At time $T_2$ when the SF-R condition clears, the K-byte values that nodes E and F receive indicate to both nodes E and F that they are head-ends of a unidirectional SF condition on the span, which pre-empts WTR. For this condition, the SF-R priority must be signalled on the long path and RR-R on the short path (Rule S #3). These actions cause crossing RR-R on the short path between nodes E and F. The WTR period for both head-ends (due to simultaneous clearing) is entered after they receive a crossing RR-R from the node that was its tail-end. At time $T_3$ , the WTR intervals expire. Both nodes react as head-ends to the WTR by sourcing the WTR priority on the long path and RR-R on the short path. Upon receiving the crossing RR-R, nodes E and F drop their ring switch and send No Request codes (Rule I-S #2). Node E, upon reception of the NR code from node F on the long path, drops its bridge and sources the Idle code (Rule I-S #2). Node F, upon reception of the NR code from E on the long path, drops its bridge and sources the Idle code (Rule I-S #2). All nodes then cascade back to the idle state. + +## **I.4 Unidirectional signal degrade (ring)** + +See Figure I.4. + +In this example, a ring switch is executed and cleared for a ring SD condition in a two-fibre ring, and for a ring SD condition over the working and protection channels in a four-fibre ring. + +The initial state of the ring is the idle state. At time $T_1$ , node F detects a ring SD condition. It becomes a switching node (Rule I-S #1) and sends bridge requests in both directions (Rule S #1). Node G, and all successive intermediate nodes on the long path, enter full pass-through (Rule I-P #1). Node E, upon reception of the bridge request from node F on the short path, transmits an SD ring bridge request on the long path, and a Reverse Request on the short path (Rule S #3). Node E, upon reception of the bridge request from node F on the long path, executes a ring bridge and updates byte K2 bits 6-8 (Rule I-S #1b). Node F, upon reception of the bridge acknowledgment from node E on the long path, executes a ring switch, and updates its K-byte signalling (Rule I-S #1b). Node E, upon reception on the long path of the bridge acknowledgment from node F, completes the switch. Signalling reaches steady-state. + +For transoceanic applications, the switching activities that would take place at the intermediate nodes. On all AU-4 protection channels not being used to protect working channels, extra traffic is restored using the DCC. + +Clearing is identical to the clearing of a unidirectional SF-R condition. + +## **I.5 Node failure** + +See Figure I.5. + +This example covers the case of a node failure in both two- and four-fibre rings. Node failure here means that all transmission, incoming and outgoing, to and from the node has failed, affecting both working and protection channels, and the node itself has lost all provisioned information. + +The initial state of the ring is the idle state. At time $T_1$ , both nodes E and G detect an SF condition on their working and protection channels. They become switching nodes (Rule I-S #1) and source bridge requests on both the short and long paths (Rule S #1). Nodes A and D, and all successive intermediate nodes on the long path enter full pass-through (Rule I-P #1). Node E, upon reception of the bridge request from node G on the long path, squelches all potentially misconnected traffic, executes a ring bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Node G, upon + +reception of the bridge request from node E on the long path, squelches all potentially misconnected traffic, executes a ring bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Signalling reaches steady state. + +For transoceanic applications, the switching activities that would take place at the intermediate nodes. On all AU-4 protection channels not being used to protect working channels, extra traffic is restored using the DCC. + +At time $T_2$ , the failed node has recovered physically but has not fully recovered its provisioning information, preventing the recovering node from proper K-byte signalling. Until the recovering node is capable of proper K-byte signalling in accordance with the current state of the ring, default APS codes are transmitted (Rule I-S #3). Nodes E and G detect the physical clearing of the signal from node F, but also receive default APS codes. As long as nodes E and G receive the default APS codes, they do not declare the defect cleared (Rule I-S #4). Signalling reaches steady state. + +At time $T_3$ , node F has fully recovered and signals appropriately. Nodes E and G receive non-default APS codes and declare the defect cleared. The WTR intervals at nodes E and G are pre-empted by the higher priority long-path bridge requests, causing nodes E and G to drop their ring bridge and switch, stop squelching and go into full pass-through (Rule S-P #1f). After Nodes E and G go into full pass-through, Node F receives long path bridge requests destined to itself from both E and G and takes no action (Rule I-S #5). When Node F receives the same signals which it is sending, it then signals the Idle code in both directions (Rule I-S #6). All nodes then cascade back to the idle state. + +## **I.6 Unidirectional SF-R pre-empting a unidirectional SD-S on non-adjacent spans** + +See Figure I.6. + +This example covers the case of a unidirectional signal fail - ring condition on a four-fibre ring pre-empting a unidirectional signal degrade - span condition that had previously existed on a non-adjacent span. + +The initial state of the ring is the idle state. At time $T_1$ , node D detects an SD-S condition on its working channels from node C. The signalling proceeds in as shown in Figure I.1, except that: + +- 1) the switching nodes become nodes C and D, not nodes E and F; and +- 2) the bridge request becomes SD-S, not SF-S. + +Signalling reaches steady-state. + +At time $T_2$ , Node F detects an SF condition on its working and protection channels from Node G. Node F becomes a switching node (Rule S-P #2b) and sources bridge requests in both directions (Rule S #1). Node G, upon seeing the short-path ring request from node F, also becomes a switching node (Rule S-P #2b). Node G sources Reverse Request back on the short path, and SF-R on the long path (Rule S #3). Intermediate nodes A, B, and E change from K-byte pass-through to full pass-through (Rule P-P #1). Node D, upon seeing a higher priority ring bridge request, drops its span switch, updates byte K2 bits 6-8, and sources No Request in both directions (Rule S-S #2c). Node C, upon seeing a No Request and dropped switch from node D, drops its bridge and switch, updates byte K2 bits 6-8, and acts on its highest priority input (Rule S-S #2d, first point) to source No Request. Node C eventually sees a ring bridge request destined to node F, but this does not change Node C's signalling (Rule S-P #1a). Node D, upon seeing a dropped switch at node C, drops its bridge and acts on its highest priority input (Rule S-S #2e) to enter full pass-through. Node C, upon seeing the dropped bridge from node D, acts on its highest priority input (Rule S-P #1b) to enter full pass-through. With all the intermediate nodes in full pass-through, nodes F and G finally receive long-path ring bridge requests. Nodes F and G each execute a bridge and switch (Rule I-S #1b, second point) and update byte K2 bits 6-8. Signalling reaches steady state. + +At time $T_3$ , the SF condition on the working and protection channels from node E to node F clears. Node F enters Wait-to-Restore (Rule S-S #3a). Node G, upon seeing the WTR bridge request from node F, also enters Wait-to-Restore (Rule S-S #3b). Node D, upon seeing two WTR bridge requests which are lower priority than its locally detected SD condition, becomes a switching node [Rule S-P #2a, point 2)], and signals appropriately. Node C, upon seeing a higher priority span bridge request destined to it, also becomes a switching node [Rule S-P #2a, point 2)], executes a span bridge, and updates byte K2 bits 6-8 (Rule I-S #1b). Node F loses its long path ring bridge request due to the span bridge request status from Node D. Node F drops its bridge and switch (Rule S #5), terminates its WTR signalling, and enters K-byte pass-through (Rule S #8). Similarly, when Node G loses its long-path ring bridge request, it drops its bridge and switch (Rule S #5), terminates its WTR signalling, and enters bidirectional K-byte pass-through. Node D, upon seeing a Bridged code on the short path from node C, executes a span bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Node C, upon seeing a Bridged and Switched code from node D, completes the process by executing a span switch and updating byte K2 bits 6-8 (Rule I-S #1b). Intermediate nodes A, E, and B then move from full pass-through to K-byte pass-through. Signalling reaches the same steady state as found at time $T_1$ . + +At time $T_4$ (not shown), the span SD condition on the working channels from node C to node D clears. The signalling proceeds in a manner as shown at time $T_2$ in Figure I.1, except that: + +- 1) the switching nodes become nodes C and D, not nodes E and F; and +- 2) the bridge request becomes SD-S, not SF-S. + +## **I.7 Unidirectional SF-S pre-empting a unidirectional SF-R on adjacent spans – SF-S and SF-R detected at non-adjacent nodes** + +See Figure I.7. + +This example covers the case of a unidirectional signal fail - span condition on a four-fibre ring pre-empting a unidirectional signal fail - ring condition that had previously existed on an adjacent span. + +The initial state of the ring is the idle state. At time $T_1$ , node C detects an SF condition on its working and protection channels from node D. The signalling proceeds in a manner as shown in Figure I.2 (at time $T_1$ in the figure), except that the switching nodes become nodes C and D, not nodes E and F. Signalling reaches steady-state. + +At time $T_2$ , Node E detects an SF condition on its working channels from node D. Node E becomes a switching node [Rule S-P #2a, point 2)] and sources a span bridge request towards node D and a span bridge request status towards node F (Rules S #1, G #1). Node C, upon seeing this span bridge request status, drops its ring bridge and switch because it is no longer receiving a long-path ring bridge request (Rule S #5). Node C updates its byte K2 bits 6-8, and sources SF-R in byte K1 because that is its highest priority input (Rule S #5). Node D, upon seeing the higher priority span bridge request from node E, drops its ring bridge and switch, executes a span bridge towards node E (Rule S-S #2f), and signals accordingly (Rule I-S #1b, third point, and Rule S #3). Node E, upon seeing the Bridged code from node D, executes a span bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b, third point). Node D, upon seeing the Bridged code from node E, executes a switch, and updates byte K2 bits 6-8 accordingly (Rule I-S #1b, third point). Signalling reaches steady state. + +At time $T_3$ , the SF condition on the working channels from node D to node E clears. Node E would enter Wait-to-Restore, but it detects another failure (Rule S-S #3a). Node E, upon seeing the SF-R bridge request destined to node D (for a span which is non-adjacent), drops its span switch, signals No Request in byte K1, and Bridged in byte K2 (Rule S-S #2c). Node D, upon seeing the No Request and Bridged codes from node E, drops its span bridge and switch, and acts on the input from node C to signal a ring bridge request back to node C (Rule S-S #2d). Node E, upon seeing that + +node D has dropped its switch, drops its bridge (Rule S-S #2e). Node E also sees a long-path ring bridge request destined to node D, so node E also enters full pass-through (Rule S-S #2e, fourth point). Node D, upon seeing a long-path ring bridge request from node C, executes a ring bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Node C, upon seeing a long-path ring bridge request from node D, also executes a ring bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Signalling reaches the same steady state found at time T1. + +At time T4 (not shown), the SF condition on the working and protection channels from node D to node C clears. The signalling proceeds in a manner as shown in Figure I.2 (at time T2 in the figure), except that the switching nodes become nodes C and D, not nodes E and F. + +## I.8 Unidirectional SF-R pre-empting a unidirectional SD-S on adjacent spans + +See Figure I.8. + +This example covers the case of a unidirectional signal fail - ring condition on a four-fibre ring pre-empting a unidirectional signal degrade - span condition that had previously existed on an adjacent span. + +The initial state of the ring is the idle state. At time T1, node F detects an SD condition on its working channels from node E. The signalling proceeds in a manner as shown in Figure I.1 (at time T1 in the figure), except that the bridge request becomes SD-S, not SF-S. Signalling reaches steady-state. + +At time T2, node E detects an SF condition on its working and protection channels from node D. Node E drops its span switch, sources a Signal Fail ring bridge request (in byte K1) and MS RDI (in byte K2) towards Node D, and sources No Request (in byte K1) and Bridged (in byte K2) towards Node F (Rule S-S #2b). Node D becomes a switching node [Rule S-P #2b, point 3)]. Node D sources Reverse Request on the short path, and a Signal Fail ring bridge request on the long path (Rule S #3). This long-path ring bridge request changes nodes C, B, and A from K-byte pass-through to full pass-through (Rule P-P #1). Node F, upon seeing a No Request and dropped switch from node E, drops its bridge and switch, updates byte K2 bits 6-8, and acts on its highest priority input (Rule S-S #2d, last point) to source a Signal Degrade span bridge request towards node E. Node E, upon seeing a dropped switch at node F, drops its bridge, updates byte K2 bits 6-8, and acts on its highest priority input (Rule S-S #2e, third point) to source ring bridge requests in both directions. Node F, upon seeing the dropped bridge from Node E, acts on its highest priority input (Rule S-P #1b) to enter full pass-through. This permits a long-path ring bridge request to reach node G, and node G changes from K-byte pass-through to full pass-through (Rule P-P #1). With all the intermediate nodes in full pass-through, nodes E and D finally receive long-path ring bridge requests. Nodes E and D each execute a bridge and switch (Rule I-S #1b, second point) and update byte K2 bits 6-8. Signalling reaches steady state. + +At time T3, the SF condition on the working and protection channels from node D to node E clears. Node E starts its Wait-to-Restore period, and signals so (Rule S-S #3a). Node D, upon seeing the WTR bridge request from node E, also starts its Wait-to-Restore period, and signals so (Rule S-S #3b). Node F, upon seeing WTR bridge requests from both directions, acts on the fact that its local SD-S condition is higher priority, and becomes a span switching node [Rule S-P #2a, point 2)]. Node E, upon seeing the span bridge request from node F, loses its long-path ring bridge request from Node D. Node E therefore drops its ring bridge and switch (Rule S #5), and acts on the span bridge request from node F by executing a span bridge (Rule I-S #1b, third point). Node F, upon seeing the Bridged code from node F, executes a span bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b, third point). Node E, upon seeing the Bridged and Switched codes from node F, completes the process by executing a span switch and updating byte K2 bits 6-8 (Rule I-S #1b, third point). Meanwhile, node D, upon seeing the span bridge request from node F, loses its long-path ring + +bridge request from node E. Node D therefore drops its ring bridge and switch (Rule S #5), and acts on the span bridge request status destined to node E by entering K-byte pass-through (Rule S-P #1g). Intermediate full pass-through nodes A, B, C and G eventually receive a span bridge request status not destined to them from both directions, so they move into K-byte pass-through. Signalling reaches the same steady state found at time $T_1$ . + +At time $T_4$ (not shown), the SD condition on the working channels from node E to node F clears. The signalling proceeds in a manner as shown in Figure I.1 (at time $T_2$ in the figure), except that the bridge request becomes SD-S, not SF-S. + +## I.9 Unidirectional SF-R coexisting with a unidirectional SF-R on non-adjacent spans + +See Figure I.9. + +This example covers the case of a unidirectional signal fail - ring condition on a four-fibre ring coexisting with another unidirectional signal fail - ring condition that had previously existed on a non-adjacent span. + +The initial state of the ring is the idle state. At time $T_1$ , node F detects an SF condition on its working and protection channels. The signalling proceeds in a manner as shown in Figure I.2 (at time $T_1$ in the figure). The signalling reaches steady state. + +At time $T_2$ , node C detects an SF condition on its working and protection channels. Node C becomes a switching node [Rule S-P #2a, point 2)], squelches traffic if necessary, executes a ring bridge and switch, and sources ring bridge requests in both directions (S-P #3). Node B, upon seeing the bridge request from node C, becomes a switching node [Rule S-P #2a, point 3)]. Node B also squelches traffic if necessary, executes a ring bridge and switch, and sources ring bridge requests in both directions (S-P #3). The long-path ring bridge request from nodes B and C do not affect the bridges and switches at nodes E and F, because multiple SF-R switches are allowed to coexist (Rule S #4a, Rule S #5). The signalling reaches steady state. + +For transoceanic applications, there is some additional signalling that occurs. As shown in Figure I.10, at time $T_2$ , node C detects an SF condition on its working and protection channels. Node C becomes a switching node [Rule S-P #2a, point 2)], drops extra traffic if present, maintains ring bridges and switches on the tributaries affected by the first failure, and sources ring bridge requests in both directions (Rule S-P #3 in Annex A). Node B, upon seeing the bridge request from Node C, becomes a switching node [Rule S-P #2a, point 3)]. Node B also drops extra traffic if present, maintains ring bridges and switches on the tributaries affected by the first failure, and sources ring bridge requests in both directions (Rule S-P #3 in Annex A). Node E (F), upon seeing the ring bridge request from node C (B), drops extra traffic if present, maintains ring bridges and switches on the tributaries affected by the first failure, and updates byte K2 bits 6-8 to the Idle code [Rule S-S #1a, point 2), in Annex A]. Node C (B), upon seeing the ring bridge request and an Idle code from node E (F), updates byte K2 bits 6-8 to Bridged and Switched [Rule S-S #1a, point 2), in Annex A]. Node E (F), upon seeing the ring bridge request and the Bridged and Switched code from node C (B), updates byte K2 bits 6-8 to Bridged and Switched [Rule S-S #1a, point 3), in Annex A]. Signalling reaches the same steady state as described for Figure I.9. + +At time $T_3$ , the SF condition on the working and protection channels from node B to node C clears. Node C sees from node D a ring bridge request for a non-adjacent span. This is a higher priority than its local (WTR) condition, so node C drops its bridge and switch and enters full pass-through (Rule S-P #1e). This permits the short-path ring Reverse Request signal from node B to reach node E. Node E still considers this to be a valid ring bridge request, so Node E retains its ring bridge and switch (Rule S #5). Node B, upon receiving both ring bridge requests that are not destined to it, + +drops its bridge and switch and enters full pass-through (Rule S-P #1f). Signalling reaches the same steady state as found at time T1. + +For transoceanic applications, the signalling is identical, but the nodes have additional actions to perform. As shown in Figure I.10, at time T3, the SF condition on the working and protection channels from node B to node C clears. Node C sees from node D a ring bridge request for a non-adjacent span, due to the first SF-R between nodes E and F. This is a higher priority than its local (WTR) condition, so node C maintains ring bridges and switches on the tributaries affected by the first failure, and enters full pass-through [Rule S-P #1e, point 1), in Annex A]. This permits the short-path ring Reverse Request signal from node B to reach node E. Node E still considers this to be a valid ring bridge request, so node E retains its ring bridge and switch (Rule S #5). Node B sees ring bridge requests that are not destined to it, due to the first SF-R between nodes E and F. Node B maintains ring bridges and switches on the tributaries affected by the first failure, and enters full pass-through [Rule S-P #1f, point 1), in Annex A]. Signalling reaches the same steady state as described for Figure I.9. + +At time T4 (not shown), the SF condition on the working and protection channels from node E to node F clears. The signalling proceeds in a manner as shown in Figure I.2 (at time T3 in the figure). + +## **I.10 Node failure on a ring with extra traffic capability (see Figure I.11)** + +Figure I.11 covers the case of extra traffic squelching on a ring after a node failure on either a two- or four-fiber ring. Node failure here means that all transmission, incoming and outgoing, to and from the node has failed, affecting both working and protection channels, and the node itself has lost all provisioned information. + +The initial state of the ring is the idle state. Extra traffic is supported on the protection channels around the ring. At time T1, both nodes E and G detect an SF condition on their working and protection channels. Nodes E and G drop extra traffic bidirectionally, become switching nodes (Rule I-S #1a, S #7), and source bridge requests on the long and short paths. All intermediate nodes will drop extra traffic bidirectionally, and enter into unidirectional full pass-through (Rule I-P #1). Non-LO VC access nodes enter bidirectional full pass-through upon receiving crossing K-bytes. Node E, upon reception of the bridge request from G on the long path, squelches all potentially misconnected traffic, executes a ring bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Node G, upon reception of the bridge request from E on the long path squelches all potentially misconnected traffic, executes a ring bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Signalling reaches steady state. + +At time T2, the failed node has recovered and the recovery sequence proceeds as per normal node recovery. Extra traffic is unsquelched when the node receives No Request and Idle or ET code from both directions. + +## **I.11 Unidirectional SF-S pre-empting a unidirectional SF-R on adjacent spans – SF-S and SF-R detected at adjacent nodes** + +See Figure I.11. + +This example covers the case of a unidirectional signal fail - span condition on a four-fibre ring pre-empting a unidirectional signal fail - ring condition that had previously existed on an adjacent span. + +The initial state of the ring is the idle state. At time T1, node D detects an SF condition on its working and protection channels from node C. The signalling proceeds in a manner as shown in Figure I.2 (at time T1 in the figure), except that the switching nodes become nodes C and D, not nodes E and F. Signalling reaches steady state. + +At time $T_2$ , node E detects a SF condition on its working channel from node D. Node E becomes a switching node (Rule S-P #2a) and sources a span bridge request towards node D and a span bridge request status towards node F destined for node D (Rules S #1, G #1). Node D, upon seeing the higher priority span bridge request from node E, drops its ring bridge and switch, and signals based on its highest allowed coexisting APS requests (Rules G #1c, S-S #2h). Node D's highest priority input allowed to coexist is SF-S request from node E, and SF-P detected from node C (Rule S-S #2 h). It executes a span bridge towards node E (Rule S-S #2f), and signals accordingly (Rules I-S #1b, S #3). Node D also signals SF-P and RDI towards node C, since SF-P and SF-S are allowed to coexist (Rules S #4 a, S-S #2 h). Node C, upon losing the ring bridge request and seeing SF-P destined for it on the short path, becomes a span switching node, and responds to the span request accordingly (Rules S-P #2 b, S #1b). Node E, upon seeing the Bridged code from Node D, executes a span bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Node D, upon seeing the Bridged code from node E, executes a switch, and updates byte K2 bits 6-8 accordingly (Rule I-S #1b). Intermediate nodes enter K-byte pass through when crossing K-bytes are detected (Rule P-P #2). Signalling reaches steady state. + +At time $T_3$ , the SF condition on the working channels from node D to node E clears. Node E enters Wait-to-Restore and signals accordingly (Rule S-S #3a). Node D, upon seeing the WTR code from node E, drops its span bridge and switch, and acts on all its inputs, which is a detected SF-R and a lower priority WTR request from node E. Node D signals a ring bridge request toward node C on both the long and short path (Rule S-S #2d). Node E, upon seeing a ring bridge request destined to another node, enters bidirectional full pass-through (Rule S-P #1e). Node C, upon losing the span bridge request and seeing a long-path ring bridge request from node D, executes a ring bridge and switch, and updates byte K2 bits 6-8 (Rules S #6, I-S #1b). Node D, upon seeing a long-path ring bridge request from node C, also executes a ring bridge and switch, and updates byte K2 bits 6-8 (Rule I-S #1b). Signalling reaches the same steady state found at time $T_1$ . + +At time $T_4$ (not shown), the SF condition on the working and protection channels from node C to node D clears. The signalling proceeds in a manner as shown in Figure I.2 (at time $T_2$ in the figure), except that the switching nodes become nodes C and D, not nodes E and F. + + + +Time + +T0 + +T1 + +A B C D E F G A + +1a 2b 2a 3b 3a 4b 4a 5b 5a 6b 6a 7b 7a 1b + +8b 8a 9b 9a 10b 10a 11b 11a + +Node sourcing K1 and K2 + +Node in K-byte pass-through + +Key for transoceanic application only: + +Restore part-time traffic, as applicable, using DCC [RSOH] + +| | K1 | K2 | | +|-----|--------|-----------|-----------------------------| +| 1a | NR/B | A/S/IDLE | T 0 – Idle state | +| 1b | NR/G | A/S/IDLE | | +| 2a | NR/C | B/S/IDLE | | +| 2b | NR/A | B/S/IDLE | | +| 3a | NR/D | C/S/IDLE | | +| 3b | NR/B | C/S/IDLE | | +| 4a | NR/E | D/S/IDLE | | +| 4b | NR/C | D/S/IDLE | | +| 5a | NR/F | E/S/IDLE | | +| 5b | NR/D | E/S/IDLE | | +| 6a | NR/G | F/S/IDLE | | +| 6b | NR/E | F/S/IDLE | | +| 7a | NR/A | G/S/IDLE | | +| 7b | NR/F | G/S/IDLE | | +| 8a | SF-S/E | F/S/IDLE | T 1 – Span SF | +| 8b | SF-S/E | F/L/IDLE | | +| 9a | RR-S/F | E/S/Br | | +| 9b | SF-S/F | E/L/Br | | +| 10a | SF-S/E | F/S/Br&Sw | | +| 10b | SF-S/E | F/L/Br&Sw | | +| 11a | RR-S/F | E/S/Br&Sw | | +| 11b | SF-S/F | E/L/Br&Sw | | + +Timing diagram for Figure I.1/G.841 showing node states and K1/K2 byte sequences over time for a four-fibre MS shared protection ring. The diagram includes nodes A through G and back to A, with time markers T0 and T1. It details the sequence of events for a unidirectional failure on the working path from E to F, showing how nodes detect the failure, enter switching states, and restore traffic. To the right, a table lists the K1 and K2 byte values at various points in time, categorized into 'Idle state' (T0) and 'Span SF' (T1) periods. + + + +T1 SF + +Topology diagram showing a ring of nodes A, B, C, D, E, F, G. Node E is the source of a failure (SF) on the working path towards node F. The diagram illustrates the flow of traffic and protection signals around the ring. + +T1533840-99 + +**Figure I.1/G.841 – Four-fibre MS shared protection ring – Unidirectional failure (span) on working from E to F** + + + +Time + +A B C D E F G A + +T2 + +– Span SF clears +– WTR starts + +**S-S #3a** + +– Sends RR on the short path and WTR on long path + +**S-S #3b** + +T3 + +– WTR expires +– Drop span switch + +**I-S #2** + +– Drop span bridge & switch +– Send idle + +**I-S #2** + +– Drop span bridge +– Send idle + +**I-S #2** + +**I-P #2** + +**I-P #2** + +– Revert to idle + +**I-P #2** + +– Revert to idle + +**I-P #2** + +– Revert to idle + +**I-S #2** + +**I-P #2** + +– Revert to idle + +**I-S #2** + +– Revert to idle + +T0 + +| | K1 | K2 | | +|-----|--------|-----------|---------------------------------| +| 10a | SF-S/E | F/S/Br&Sw | T 1 – Steady state | +| 10b | SF-S/E | F/L/Br&Sw | | +| 11a | RR-S/F | E/S/Br&Sw | | +| 11b | SF-S/F | E/L/Br&Sw | | +| 12a | WTR/E | F/S/Br&Sw | T 2 – Span SF clears | +| 12b | WTR/E | F/L/Br&Sw | | +| 13b | WTR/F | E/L/Br&Sw | T 3 – WTR expires | +| 14a | NR/E | F/S/Br | | +| 14b | NR/E | F/L/Br | | +| 1a | NR/B | A/S/IDLE | T 0 – Idle state | +| 1b | NR/G | A/S/IDLE | | +| 2a | NR/C | B/S/IDLE | | +| 2b | NR/A | B/S/IDLE | | +| 3a | NR/D | C/S/IDLE | | +| 3b | NR/B | C/S/IDLE | | +| 4a | NR/E | D/S/IDLE | | +| 4b | NR/C | D/S/IDLE | | +| 5a | NR/F | E/S/IDLE | | +| 5b | NR/D | E/S/IDLE | | +| 6a | NR/G | F/S/IDLE | | +| 6b | NR/E | F/S/IDLE | | +| 7a | NR/A | G/S/IDLE | | +| 7b | NR/F | G/S/IDLE | | + +→ Node sourcing K1 and K2 + +– – – –> Node in K-byte pass-through + +Key for transoceanic application only: + +**– – – – –** Restore part-time traffic, as applicable, using DCC [RSOH] + +G A B + +F + +E D C + +T1 SF + +X + +T1533850-99 + +Timing diagram for a four-fibre MS shared protection ring showing node states and traffic flow over time. The diagram includes a sequence of nodes A through G and back to A. It marks key time points T2, T3, and T0. On the right, tables show K1 and K2 byte values for various states: Steady state (10a-11b), Span SF clears (12a-12b), WTR expires (13b), and Idle state (1a-7b). A legend at the bottom left explains line types: solid for K1/K2 sourcing, dashed for pass-through, and dashed-dotted for restore traffic. A small network diagram at the bottom right shows nodes A, B, C, D, E, F, G with a failure 'X' on the E-F link. Network diagram showing nodes A, B, C, D, E, F, G in a ring. A failure 'X' is marked on the working fiber between E and F. T1 SF is indicated at node F. + +**Figure I.1/G.841 – Four-fibre MS shared protection ring – +Unidirectional failure (span) on working from E to F (concluded)** + + + +**T0 – Idle state** + +| K1 | K2 | +|----|---------------| +| 1a | NR/B A/S/IDLE | +| 1b | NR/G A/S/IDLE | +| 2a | NR/C B/S/IDLE | +| 2b | NR/A B/S/IDLE | +| 3a | NR/D C/S/IDLE | +| 3b | NR/B C/S/IDLE | +| 4a | NR/E D/S/IDLE | +| 4b | NR/C D/S/IDLE | +| 5a | NR/F E/S/IDLE | +| 5b | NR/D E/S/IDLE | +| 6a | NR/G F/S/IDLE | +| 6b | NR/E F/S/IDLE | +| 7a | NR/A G/S/IDLE | +| 7b | NR/F G/S/IDLE | + +**T1 – Ring SF** + +| K1 | K2 | +|-----|------------------| +| 8a | SF-R/E F/S/RDI | +| 8b | SF-R/E F/L/IDLE | +| 9a | RR-R/F E/S/IDLE | +| 9b | SF-R/F E/L/IDLE | +| 10a | RR-R/F E/S/Br&Sw | +| 10b | SF-R/F E/L/Br&Sw | +| 11a | SF-R/E F/S/RDI | +| 11b | SF-R/E F/L/Br&Sw | + +**T2 – Ring SF clears** + +| K1 | K2 | +|-----|-----------------| +| 12a | WTR/E F/S/Br&Sw | +| 12b | WTR/E F/L/Br&Sw | +| 13b | WTR/F E/L/Br&Sw | + +Timing diagram for Figure I.2/G.841 showing signal paths and states across nodes A through G over time. The diagram is divided into three main time intervals: T0 (Idle state), T1 (Ring SF), and T2 (Ring SF clears). Nodes are labeled A, B, C, D, E, F, G, A. Signal paths are shown as lines with arrows indicating direction. States are indicated by labels like I-P #1, I-S #1a, I-S #1b, S-S #3a, S-S #3b. K1 and K2 byte values are shown in tables on the right for each interval. + +→ Node sourcing K1 and K2 + → Node in full pass-through, K1, K2 and protection channels + +Key for transoceanic application only: + +\* Br&Sw at intermediate nodes if working traffic is affected by failure + +--- Restore part-time traffic, as applicable, using DCC [RSOH] + ++ Start local WTR interval at intermediate nodes if they have active Br&Sw + +NOTE – See Tables 7-7 and 7-8 for bytes K1 and K2 formats. + + + +Topology diagram showing a unidirectional SF ring with nodes A, B, C, D, E, F, G. Node A is the source of K1 and K2. Node B is in full pass-through. Nodes C, D, E, F, G are intermediate nodes. The diagram shows the flow of traffic and protection signals around the ring. + +T1533860-99 + +**Figure I.2/G.841 – Two- or four-fibre MS shared protection ring – Unidirectional SF (ring)** + + + +Timing diagram showing the sequence of events for a unidirectional SF ring. The vertical axis represents Time, with markers $T_3$ , $T_2$ , and $T_0$ . Nodes are labeled A, B, C, D, E, F, G, and A (return). The diagram illustrates the transition between 'Steady state' and 'Idle state' following a failure and subsequent recovery. Key actions include 'WTR expires', 'Drop ring bridge and switch', 'Send idle', and 'Revert to idle'. Signal flow is shown with arrows, and specific states are indicated by labels like 'I-P #2' and 'I-S #2'. + +| State | K1 | K2 | +|--------------|--------|-----------| +| Steady state | RR-R/F | E/S/Br&Sw | +| | WTR/E | F/S/Br&Sw | +| | WTR/E | F/L/Br&Sw | +| | WTR/F | E/L/Br&Sw | +| WTR expires | NR/E | F/S/Br | +| | NR/E | F/L/Br | +| Idle state | NR/B | A/S/IDLE | +| | NR/G | A/S/IDLE | +| | NR/C | B/S/IDLE | +| | NR/A | B/S/IDLE | +| | NR/D | C/S/IDLE | +| | NR/B | C/S/IDLE | +| | NR/E | D/S/IDLE | +| | NR/C | D/S/IDLE | +| | NR/F | E/S/IDLE | +| | NR/D | E/S/IDLE | +| | NR/G | F/S/IDLE | +| | NR/E | F/S/IDLE | +| | NR/A | G/S/IDLE | +| | NR/F | G/S/IDLE | + +Timing diagram for a unidirectional SF ring showing node states and signal flow over time. The diagram includes nodes A through G and a return to A. It shows various states like 'Steady state', 'WTR expires', and 'Idle state' with corresponding K1 and K2 byte values. Signal flow is indicated by arrows, and specific actions like 'Drop ring bridge and switch' or 'Revert to idle' are noted at nodes. + +→ Node sourcing K1 and K2 + → Node in full pass-through, K1, K2 and protection channels + +Key for transoceanic application only: + +..... Drop Sw at intermediate nodes at WTR/2, if applicable + +~ Drop Br at intermediate nodes, if applicable + +----- Restore part-time traffic, as applicable, using DCC [RSOH] + + + +Topology diagram of a unidirectional SF ring. Nodes are labeled A, B, C, D, E, F, and G. The ring is unidirectional, with traffic flowing from G through A, B, C, D, E, F, and back to G. A failure is indicated by an 'X' on the link between F and E. The label 'T1 SF' is present near node E. + +Topology diagram of a unidirectional SF ring showing nodes A, B, C, D, E, F, and G. Node G is the source, and traffic flows clockwise through A, B, C, D, E, F, and back to G. A failure is indicated by an 'X' on the link between F and E, and a 'T1 SF' label is present near node E. + +T1533870-99 + +Figure I.2/G.841 – Two- or four-fibre MS shared protection ring – Unidirectional SF (ring) (concluded) + + + +**Time** + +**T0** + +**T1** + +**T2** + +**Nodes:** A B C D E F G A + +| | K1 | K2 | T 0 – Idle state | +|-----|--------|-----------|---------------------------------| +| 1a | NR/B | A/S/IDLE | | +| 1b | NR/G | A/S/IDLE | | +| 2a | NR/C | B/S/IDLE | | +| 2b | NR/A | B/S/IDLE | | +| 3a | NR/D | C/S/IDLE | | +| 3b | NR/B | C/S/IDLE | | +| 4a | NR/E | D/S/IDLE | | +| 4b | NR/C | D/S/IDLE | | +| 5a | NR/F | E/S/IDLE | | +| 5b | NR/D | E/S/IDLE | | +| 6a | NR/G | F/S/IDLE | | +| 6b | NR/E | F/S/IDLE | | +| 7a | NR/A | G/S/IDLE | | +| 7b | NR/F | G/S/IDLE | | +| | | | | +| 8a | SF-R/F | E/S/RDI | T 1 – Ring SF | +| 8b | SF-R/F | E/L/IDLE | | +| 9a | SF-R/E | F/S/RDI | | +| 9b | SF-R/E | F/L/IDLE | | +| 10b | SF-R/F | E/L/Br&Sw | | +| 11b | SF-R/E | F/L/Br&Sw | | +| | | | | +| 10a | RR-R/F | E/S/Br&Sw | T 2 – Ring SF clears | +| 11a | RR-R/E | F/S/Br&Sw | | +| 12a | WTR/F | E/S/Br&Sw | | +| 12b | WTR/F | E/L/Br&Sw | | +| 13a | WTR/E | F/S/Br&Sw | | +| 13b | WTR/E | F/L/Br&Sw | | + +Node sourcing K1 and K2 + Node in full pass-through, K1, K2 and protection channels + +Key for transoceanic application only: + +- \* Br&Sw at intermediate nodes if working traffic is affected by failure +- Restore part-time traffic, as applicable, using DCC [RSOH] +- + Start local WTR interval at intermediate nodes if they have active Br&Sw + +NOTE – See Tables 7-7 and 7-8 for bytes K1 and K2 formats. + +T1533880-99 + +Timing diagram for Two- or four-fibre MS shared protection ring - Bidirectional SF (ring). The diagram shows signal flow between nodes A through G over time, with specific events labeled like I-P #1, I-S #1a, I-S #1b, S #3, and S-S #3a. A state transition table on the right shows K1 and K2 byte values for different states like Idle, Ring SF, and Ring SF clears. A legend at the bottom explains symbols for node types and actions like Br&Sw and WTR. Solid arrow Dashed arrow Dashed line Ring topology diagram showing nodes A, B, C, D, E, F, G in a ring. A failure (SF) is shown between nodes E and F at time T1. + +**Figure I.3/G.841 – Two- or four-fibre MS shared protection ring – Bidirectional SF (ring)** + + + +Time + +Nodes: A, B, C, D, E, F, G, A + +States shown: S #3, I-S #2, I-P #2 + +Key for transoceanic application only: + +- ..... Drop Sw at intermediate nodes at WTR/2, if applicable +- ~ Drop Br at intermediate nodes, if applicable +- - - - - Restore part-time traffic, as applicable, using DCC [RSOH] + +Legend: + +- Node sourcing K1 and K2 +- Node in full pass-through, K1, K2 and protection channels + +Network Topology: Nodes A, B, C, D, E, F, G in a ring. Node F has a failure (SF). + +State Transition Table: + +| | K1 | K2 | | +|-----|--------|-----------|----------------------| +| 12a | WTR/F | E/S/Br&Sw | $T_2$ – Steady state | +| 12b | WTR/F | E/L/Br&Sw | | +| 13a | WTR/E | F/S/Br&Sw | | +| 13b | WTR/E | F/L/Br&Sw | | +| 12c | RR-R/F | E/S/Br&Sw | $T_3$ – WTR expires | +| 13c | RR-R/E | F/S/Br&Sw | | +| 14a | NR/F | E/S/Br | | +| 14b | NR/F | E/L/Br | | +| 15a | NR/E | F/S/Br | Idle state | +| 15b | NR/E | F/L/Br | | +| 1a | NR/B | A/S/IDLE | | +| 1b | NR/G | A/S/IDLE | | +| 2a | NR/C | B/S/IDLE | Idle state | +| 2b | NR/A | B/S/IDLE | | +| 3a | NR/D | C/S/IDLE | | +| 3b | NR/B | C/S/IDLE | | +| 4a | NR/E | D/S/IDLE | Idle state | +| 4b | NR/C | D/S/IDLE | | +| 5a | NR/F | E/S/IDLE | | +| 5b | NR/D | E/S/IDLE | | +| 6a | NR/G | F/S/IDLE | Idle state | +| 6b | NR/E | F/S/IDLE | | +| 7a | NR/A | G/S/IDLE | | +| 7b | NR/F | G/S/IDLE | | + +T1533890-99 + +Timing diagram for Two- or four-fibre MS shared protection ring. The diagram shows signal flow between nodes A through G over time, with various states like S #3, I-S #2, and I-P #2. A state transition table on the right lists conditions for K1 and K2 bytes across different states. A network topology diagram at the bottom right shows nodes A-G in a ring with a failure at node F. + +Figure I.3/G.841 – Two- or four-fibre MS shared protection ring – Bidirectional SF (ring) (concluded) + + + +The diagram illustrates the sequence of events in a unidirectional SD ring. The vertical axis represents time, with markers T0, T1, and T2. Nodes are labeled A, B, C, D, E, F, G, and back to A. Signal paths are shown with arrows. States are indicated by labels like I-P #1, I-S #1a, I-S #1b, S-S #3a. The right side lists K1 and K2 byte values for various states. + +| | K1 | K2 | State | +|-----|--------|-----------|-------------------------------| +| 1a | NR/B | A/S/IDLE | T 0 – Idle state | +| 1b | NR/G | A/S/IDLE | | +| 2a | NR/C | B/S/IDLE | | +| 2b | NR/A | B/S/IDLE | | +| 3a | NR/D | C/S/IDLE | | +| 3b | NR/B | C/S/IDLE | | +| 4a | NR/E | D/S/IDLE | | +| 4b | NR/C | D/S/IDLE | T 1 – Ring SD | +| 5a | NR/F | E/S/IDLE | | +| 5b | NR/D | E/S/IDLE | | +| 6a | NR/G | F/S/IDLE | | +| 6b | NR/E | F/S/IDLE | | +| 7a | NR/A | G/S/IDLE | | +| 7b | NR/F | G/S/IDLE | | +| 8a | SD-R/E | F/S/IDLE | T 2 Ring SD clears | +| 8b | SD-R/E | F/L/IDLE | | +| 9a | RR-R/F | E/S/IDLE | | +| 9b | SD-R/F | E/L/IDLE | | +| 10a | RR-R/F | E/S/Br | | +| 10b | SD-R/F | E/L/Br | | +| 11a | SD-R/E | F/S/Br | | +| 11b | SD-R/E | F/L/Br | | +| 12a | SD-R/E | F/S/Br&Sw | | +| 12b | SD-R/E | F/L/Br&Sw | | +| 13a | RR-R/F | E/S/Br&Sw | | +| 13b | SD-R/F | E/L/Br&Sw | | +| 14a | WTR/E | F/S/Br&Sw | | +| 14b | WTR/E | F/L/Br&Sw | | + +Timing diagram for Two- or four-fibre MS shared protection ring - Unidirectional SD (ring). The diagram shows signal flow across nodes A through G over time, with states T0 (Idle), T1 (Ring SD), and T2 (Ring SD clears). It includes K1 and K2 byte sequences and node actions like 'Detect SD', 'Ring bridge', and 'Ring switch'. + +- Node sourcing K1 and K2 +- Node in full pass-through, K1, K2 and protection channels +- Key for transoceanic application only: + - # Br at intermediate nodes if working traffic is affected by failure + - ^ Sw at intermediate nodes if working traffic is affected by failure +- - - - Restore part-time traffic, as applicable, using DCC [RSOH] + +NOTE – See Tables 7-7 and 7-8 for bytes K1 and K2 formats. + + + +The topology diagram shows a ring of nodes: A, B, C, D, E, F, G. Node E has a failure symbol (X) on its T1 SD line. Signal flow is indicated by arrows between adjacent nodes in a clockwise direction. + +Topology diagram showing nodes A, B, C, D, E, F, G in a ring configuration. Node E is marked with a failure symbol (X) on the T1 SD line. Arrows indicate signal flow between nodes. + +T1533900-99 + +Figure I.4/G.841 – Two- or four-fibre MS shared protection ring – Unidirectional SD (ring) + + + +**Idle state (T0 to T1)** + +| K1 | K2 | +|----|---------------| +| 1a | NR/B A/S/IDLE | +| 1b | NR/G A/S/IDLE | +| 2a | NR/C B/S/IDLE | +| 2b | NR/A B/S/IDLE | +| 3a | NR/D C/S/IDLE | +| 3b | NR/B C/S/IDLE | +| 4a | NR/E D/S/IDLE | +| 4b | NR/C D/S/IDLE | +| 5a | NR/F E/S/IDLE | +| 5b | NR/D E/S/IDLE | +| 6a | NR/G F/S/IDLE | +| 6b | NR/E F/S/IDLE | +| 7a | NR/A G/S/IDLE | +| 7b | NR/F G/S/IDLE | + +**Node F fails (T1)** + +| K1 | K2 | +|-----|------------------| +| 8a | SF-R/F E/S/RDI | +| 8b | SF-R/F E/L/IDLE | +| 9a | SF-R/F G/S/RDI | +| 9b | SF-R/F G/L/IDLE | +| 10b | SF-R/F E/L/Br&Sw | +| 11b | SF-R/F G/L/Br&Sw | + +**Node F repaired (T2)** + +| K1 | K2 | +|----|--------------------------| +| D | ----/K1 ID K2 ID/ - ---- | + +Signalling from nodes E and G does not change until they receive non-default APS codes. +Default APS codes are defined as having K1 ID value = K2 ID value with the remaining bits = don't care. + +Timing diagram for a four-fibre MS shared protection ring showing node failure and recovery. The diagram spans from T0 to T2. Nodes A through G are shown. Node F fails at T1 and is repaired at T2. The diagram shows the flow of K1 and K2 bytes and protection channels (I-P #1, I-S #1a, I-S #1b, I-S #3, I-S #4) during the failure and recovery process. On the right, tables show the state of K1 and K2 bytes at various points in time, categorized into Idle state, Node F fails, and Node F repaired phases. + + + +→ Node sourcing K1 and K2 + → Node in full pass-through, K1, K2 and protection channels + Key for transoceanic application only: + \* Br&Sw at intermediate nodes if working traffic is affected by failure + - - - - - Restore part-time traffic, as applicable, using DCC [RSOH] + +NOTE – See Tables 7-7 and 7-8 for bytes K1 and K2 formats. + + + +Topology diagram of a four-fibre MS shared protection ring. Nodes A, B, C, D, E, F, and G are arranged in a ring. Node F is highlighted with a T1 label, indicating the point of failure. Arrows show the direction of traffic flow around the ring. + +T1533910-99 + +**Figure I.5/G.841 – Four-fibre MS shared protection ring – Node failure** + + + +The diagram illustrates the sequence of events in a four-fibre MS shared protection ring during a node failure. The vertical axis represents time, with a specific failure point marked as $T_3$ . Nodes are labeled A, B, C, D, E, F, G, and back to A. Node F is the failing node. The diagram shows the propagation of signals (K1, K2, and protection channels) and the resulting states (SF-R/F, NR/I, IDLE) at various nodes (S-P #1f, I-S #5, P #2, I-S #6, I-P #2) as they attempt to reroute traffic around the failure. Recovery actions like 'Revert to idle' and 'Send idle' are indicated. A note specifies that Node F sends appropriate isolated node signaling in both directions upon failure. + +Timing diagram for a four-fibre MS shared protection ring showing node failure and recovery. The diagram plots signal states across nodes A through G over time. Key events include Node F failure at T3, subsequent protection switching (S-P #1f, I-S #5, P #2, I-S #6, I-P #2), and eventual recovery. Signal types shown include SF-R/F, NR/I, and various IDLE states for K1 and K2 channels. + +| | K1 | K2 | | +|----------------------------------------------------------------------|--------|------------------------|--------------------------------------| +| 8a | SF-R/F | E/S/RDI | $T_2$ – Steady state | +| 9a | SF-R/F | G/S/RDI | | +| 10b | SF-R/F | E/L/Br&Sw | | +| 11b | SF-R/F | G/L/Br&Sw | | +| D | ---- | /K1 ID /K2 ID/ - /---- | | +| 12a | SF-R/G | F/L/IDLE | $T_3$ – Node F repaired and SW ready | +| 13a | SF-R/E | F/L/IDLE | | +| Node F sends appropriate isolated node signaling in both directions. | | | | +| 1a | NR/G | A/S/IDLE | Idle state | +| 1b | NR/B | A/S/IDLE | | +| 2a | NR/A | B/S/IDLE | | +| 2b | NR/C | B/S/IDLE | | +| 3a | NR/B | C/S/IDLE | | +| 3b | NR/D | C/S/IDLE | | +| 4a | NR/C | D/S/IDLE | | +| 4b | NR/E | D/S/IDLE | | +| 5a | NR/D | E/S/IDLE | | +| 5b | NR/F | E/S/IDLE | | +| 6a | NR/E | F/S/IDLE | | +| 6b | NR/G | F/S/IDLE | | +| 7a | NR/F | G/S/IDLE | | +| 7b | NR/A | G/S/IDLE | | + +- Node sourcing K1 and K2 +- Node in full pass-through, K1, K2 and protection channels +- Key for transoceanic application only: + - @ Drop Br&Sw at intermediate nodes, if applicable +- Restore part-time traffic, as applicable, using DCC [RSOH] + + + +This topology diagram shows the physical layout of the nodes in the ring. Nodes A, B, C, D, E, F, and G are arranged in a circular fashion. Node F is positioned on the left and has additional external connections, which are relevant for transoceanic applications. The connections between nodes form a closed loop. + +Topology diagram showing the physical arrangement of nodes A, B, C, D, E, F, and G in a ring configuration. Node F is shown with external connections, possibly representing a transoceanic link. + +T1533920-99 + +Figure I.5/G.841 – Four-fibre MS shared protection ring – Node failure (concluded) + + + +Timing diagram showing signal flow between nodes A, B, C, D, E, F, G, and A over time. The diagram illustrates the sequence of events for a four-fibre MS shared protection ring, including detection of SF-R, switching actions, and pass-through states. + +Key events and states shown: + +- Node A:** T1 (1b, 2b), T2 (1b, 2b) +- Node B:** T1 (1b, 2b), T2 (1b, 2b) +- Node C:** T1 (1b, 1a), T2 (1b, 1a) +- Node D:** T1 (2a, 2b), T2 (1b, 2b) +- Node E:** T1 (1b, 2b), T2 (1b, 2b) +- Node F:** T1 (1b, 2b), T2 (1b, 2b) +- Node G:** T1 (1b, 2b), T2 (1b, 2b) + +States and actions: + +- Node F:** - Detect SF-R, - Enter switching (3b, 3a) +- Node E:** P-P #1 (3b, 2b) +- Node D:** S-S #2c (4a, 4b) +- Node C:** - Drop span switch (6b, 6a), S-S #2d (6b, 6a) +- Node B:** P-P #1 (1b, 5b), S-P #1a (3b, 5b), - Drop span Br&Sw, - No action, - Enter full pass-through (3b, 5b), S-P #1b (3b, 5b) +- Node A:** S-P #2b(2) (3b, 3a), S-P #2b(3) (5b, 5b), - Enter switching (5b, 5b), P-P #1 (1b, 6b), I-S #1b (3b, 8b), - Ring Br&Sw (7b, 3a), I-S #1b (8a, 8b), - Ring Br&Sw (8b, 8b) + +Table of K1 and K2 byte values: + +| | K1 | K2 | | +|----|--------|-----------|--------------------------| +| 1a | RR-S/D | C/S/Br&Sw | T 1 - Span SD | +| 1b | SD-S/D | C/L/Br&Sw | | +| 2a | SD-S/C | D/S/Br&Sw | T 2 - Ring SF | +| 2b | SD-S/C | D/L/Br&Sw | | +| 3a | SF-R/G | F/S/RDI | | +| 3b | SF-R/G | F/L/IDLE | | +| 4a | NR/C | D/S/Br | | +| 4b | NR/C | D/L/Br | | +| 5a | RR-R/F | G/S/IDLE | | +| 5b | SF-R/F | G/L/IDLE | | +| 6a | NR/D | C/S/IDLE | | +| 6b | NR/B | C/S/IDLE | | +| 7b | SF-R/G | F/L/Br&Sw | | +| 8a | RR-R/F | G/S/Br&Sw | | +| 8b | SF-R/F | G/L/Br&Sw | | + +Timing diagram for a four-fibre MS shared protection ring. It shows signal flow between nodes A, B, C, D, E, F, G, and A over time. Key events include 'Detect SF-R', 'Enter switching', 'Drop span switch', 'Enter full pass-through', and 'Ring Br&Sw'. A table on the right lists K1 and K2 byte values for different states. + + + +Legend: + +- Node sourcing K1 and K2 (solid arrow) +- Node in K-byte pass-through (dashed arrow) +- Node in full pass-through, K1, K2 and protection channels (grey arrow) + +Legend for signal flow types: solid arrow for node sourcing K1 and K2, dashed arrow for node in K-byte pass-through, and grey arrow for node in full pass-through. + + + +Topology diagram showing nodes A, B, C, D, E, F, G arranged in a ring. Node G is connected to A, A to B, B to C, C to D, D to E, E to F, F to G. Arrows indicate signal flow directions. Labels include T2 SF-R, T3 SF-R Clears, and T1 SD-S. + +Topology diagram showing nodes A, B, C, D, E, F, G arranged in a ring. Node G is connected to A, A to B, B to C, C to D, D to E, E to F, F to G. Arrows indicate signal flow directions. Labels include T2 SF-R, T3 SF-R Clears, and T1 SD-S. + +T1533930-99 + +Figure I.6/G.841 – Four-fibre MS shared protection ring – Unidirectional SF-R pre-empting a unidirectional SD-S on non-adjacent spans + +Image: Sequence chart showing signal exchanges between nodes A, B, C, D, E, F, G, and A over time. The chart shows various states like 'Enter Switching', 'Span Bridge', 'Span Switch', 'Drop Ring Br&Sw', 'Enter K-byte pass-through', and 'Enter WTR'. Nodes are labeled at the top. Time flows downwards from T3. Various signal paths (K1, K2) are shown as arrows between nodes. + +The sequence chart shows the interaction between nodes A, B, C, D, E, F, G, and A over time, starting from time T3. It details the transition of states such as S-S #3a, S-S #3b, S-P #2a(2), I-S #1b, I-S #1, S #5, S #8, and P-P #2. Specific events like 'SF-R clears', 'Enter WTR', 'Enter Switching', 'Span Bridge', 'Span Switch', and 'Drop Ring Br&Sw' are marked at specific nodes and times. + +| | K1 | K2 | Section | +|-----|--------|-----------|---------------------------------| +| 1a | RR-S/D | C/S/Br&Sw | T 1 – SPAN SD | +| 1b | SD-S/D | C/L/Br&Sw | | +| 2a | SD-S/C | D/S/Br&Sw | | +| 2b | SD-S/C | D/L/Br&Sw | | +| 3a | SF-R/G | F/S/RDI | T 2 – RING SF | +| 3b | SF-R/G | F/L/IDLE | | +| 4a | NR/C | D/S/Br | | +| 4b | NR/C | D/L/Br | | +| 5a | RR-R/F | G/S/IDLE | | +| 5b | SF-R/F | G/L/IDLE | | +| 6a | NR/D | C/S/IDLE | | +| 6b | NR/D | C/L/IDLE | | +| 7a | SF-R/G | F/L/Br&Sw | | +| 7b | RR-R/F | G/S/Br&Sw | | +| 8a | SF-R/F | G/L/Br&Sw | T 3 – RING SF CLEARS | +| 8b | WTR/G | F/S/Br&Sw | | +| 9a | WTR/G | F/L/Br&Sw | | +| 9b | WTR/F | G/L/Br&Sw | | +| 10b | SD-S/C | D/S/IDLE | | +| 11a | SD-S/C | D/L/IDLE | | +| 11b | RR-S/D | C/S/Br | | +| 12a | SD-S/D | C/L/Br | | +| 12b | SD-S/D | C/L/Br | | + +Image: Solid black arrow + + Node sourcing K1 and K2 + +Image: Dashed black arrow + + Node in K-byte pass-through + +Image: Solid grey arrow + + Node in full pass-through, K1, K2 and protection channels + +Image: Network topology diagram showing nodes A, B, C, D, E, F, G arranged in a ring. Node G is connected to A and F. Node A is connected to G and B. Node B is connected to A and C. Node C is connected to B and D. Node D is connected to C and E. Node E is connected to D and F. Node F is connected to E and G. Various failure and clear conditions are marked: T2 SF-R, T3 SF-R clears, and T1 SD-S. + +**Figure I.6/G.841 – Four-fibre MS shared protection ring – Unidirectional SF-R +pre-empting a unidirectional SD-S on non-adjacent spans (*concluded*)** + +Recommendation G.841 (10/98) 119 + + + +Time A B C D E F G A + +T1 + +T2 + +T3 + +Node sourcing K1 and K2 + +Node in full pass-through, K1, K2 and protection channels + +| | K1 | K2 | | +|----|--------|-----------|---------------------------------| +| 1a | SF-R/D | C/S/RDI | T 1 - Ring SF | +| 1b | SF-R/D | C/L/Br&Sw | | +| 2a | RR-R/C | D/S/Br&Sw | | +| 2b | SF-R/C | D/L/Br&Sw | | +| 3a | SF-S/D | E/S/IDLE | T 2 - Span SF | +| 3b | SF-S/D | E/L/IDLE | | +| 4a | RR-S/E | D/S/Br | | +| 4b | SF-S/E | D/L/Br | | +| 5a | SF-S/D | E/S/Br&Sw | | +| 5b | SF-S/D | E/L/Br&Sw | | +| 6a | RR-S/E | D/S/Br&Sw | T 3 - Span SF clears | +| 6b | SF-S/E | D/L/Br&Sw | | +| 7b | SF-R/D | C/L/IDLE | | +| 8a | NR/D | E/S/Br | | +| 8b | NR/D | E/L/Br | | +| 9a | RR-R/C | D/S/IDLE | | +| 9b | SF-R/C | D/L/IDLE | | + +Sequence diagram showing four-fibre MS shared protection ring operations. The diagram plots signal paths across nodes A, B, C, D, E, F, G, and back to A over time. It shows various switching events like 'Detect SF-S', 'Enter switching', 'Drop ring Br&Sw', 'Span Br', 'Clear SF-S', 'Drop span Sw', 'Ring Br&Sw', and 'Enter full pass-through'. On the right, a table lists K1 and K2 signal states for different failure scenarios: T1 - Ring SF, T2 - Span SF, and T3 - Span SF clears. A legend at the bottom left explains the arrow types: solid for nodes sourcing K1 and K2, and dashed for nodes in full pass-through. + + + +T3 clears SF-S + +T2 SF-S + +T1 SF-R + +Topology diagram of a four-fibre MS shared protection ring. Nodes are arranged in a circle: A, B, C, D, E, F, G. Node A is the central node. Arrows indicate signal flow. Labels indicate failure conditions: T3 clears SF-S, T2 SF-S, and T1 SF-R. Red 'X' marks indicate signal paths that are blocked or preempted during failures. + +T1533950-99 + +Figure I.7/G.841 – Four-fibre MS shared protection ring – Unidirectional SF-S pre-empting a unidirectional SF-R on adjacent spans + + + +| | K1 | K2 | +|----|--------|-----------| +| 1a | RR-S/F | E/S/Br&Sw | +| 1b | SD-S/F | E/L/Br&Sw | +| 2a | SD-S/E | F/S/Br&Sw | +| 2b | SD-S/E | F/L/Br&Sw | +| 3a | SF-R/D | E/S/RDI | +| 3b | NR/F | E/S/Br | +| 4a | RR-R/E | D/S/IDLE | +| 4b | SF-R/E | D/L/IDLE | +| 5a | SD-S/E | F/S/IDLE | +| 5b | SD-S/E | F/L/IDLE | +| 6b | SF-R/D | E/L/IDLE | +| 7a | RR-R/E | D/S/Br&Sw | +| 7b | SF-R/E | D/L/Br&Sw | +| 8b | SF-R/D | E/L/Br&Sw | + +Timing diagram for a four-fibre MS shared protection ring. It shows nodes A through G in a ring. Time flows from top to bottom. Events include 'Detect SF-R', 'Enter switching', 'Drop span Br&Sw', 'Ring Br&Sw', and 'Enter full pass-through'. A table on the right shows K1 and K2 byte values for different states. Labels T1, T2, T3, SF-R, and SD-S are used to mark specific events and states. + +- Node sourcing K1 and K2 +- - - - Node in K-byte pass-through +- Node in full pass-through, K1, K2 and protection channels + + + +Topology diagram showing a ring of nodes A, B, C, D, E, F, G. Node E is the source of an SD-S signal. Node F is the source of an SF-R signal. Arrows indicate signal flow and pass-through paths between nodes. Labels T1, T2, T3, SF-R, and SD-S are present near node E. + +Figure I.8/G.841 – Four-fibre MS shared protection ring – Unidirectional SF-R pre-empting a unidirectional SD-S on non-adjacent spans + + + +The sequence diagram illustrates the temporal progression of network states across nodes A, B, C, D, E, F, and G. The vertical axis represents time, with a T3 marker at the top. The diagram is segmented into three main phases on the right side: + +- T1 - Span SD:** Includes time intervals 1a through 4b. Key events include RR-S/F, SD-S/F, SD-S/E, and SF-R/D signals. +- T2 - Ring SF:** Includes time intervals 5a through 8b. Key events include RR-R/E, SD-S/E, SF-R/D, and NR/F signals. +- T3 - Ring SF clears:** Includes time intervals 9a through 11b. Key events include WTR/D, SD-S/E, and SF-R/E signals. + +Nodes are shown as vertical lines. Signal flows are indicated by arrows: solid for K1/K2 sourcing, dashed for K-byte pass-through, and grey for full pass-through. Specific node states and actions are labeled, such as "S-S #3a", "S-P #2a(2)", "S #5 & I-S #1b", "I-S #1b", "S #5 S-P #1g", "P-P #2", and "P-P #21b". + +Sequence diagram showing the interaction between nodes A through G over time for a four-fibre MS shared protection ring. The diagram is divided into three phases: T1 - Span SD, T2 - Ring SF, and T3 - Ring SF clears. It shows various signal flows (K1, K2, protection channels) and state changes (SF-R clears, WTR starts, SD-S #3a, S-P #2a(2), etc.). + +- Node sourcing K1 and K2 +- - - -> Node in K-byte pass-through +- Node in full pass-through, K1, K2 and protection channels + + + +This topology diagram shows the physical arrangement of nodes A, B, C, D, E, F, and G in a ring. Node E is the focal point, with labels indicating the sequence of events: T1 SD-S, T2 SF-R, and T3 SF-R clears. Arrows show the clockwise flow of signals between nodes. + +Topology diagram showing nodes A, B, C, D, E, F, and G arranged in a ring. Node E is highlighted with 'T1 SD-S', 'T2 SF-R', and 'T3 SF-R clears' labels. Arrows indicate the direction of signal flow between adjacent nodes. + +T1533970-99 + +Figure I.8/G.841 – Four-fibre MS shared protection ring – Unidirectional SF-R pre-empting a unidirectional SD-S on non-adjacent spans (concluded) + + + +Sequence diagram showing the operation of a four-fibre MS shared protection ring. The diagram plots nodes A, B, C, D, E, F, G, A over time (T1, T2, T3). It shows signal flows for K1, K2, and protection channels. Key events include: at T2, node C detects SF-R and enters switching (S-P #2a(2), S-P #3); at T3, node C clears SF-R and drops ring Br&Sw (S-P #1e); node B enters full pass-through (S-P #1f). A legend on the right maps channel numbers (10a, 10b, 11a, 11b, 12a, 12b, 13a, 13b) to K1 and K2 functions for the first and second ring SF. A 'No action S #5' is noted at node E. + +→ Node sourcing K1 and K2 + → Node in full pass-through, K1, K2 and protection channels + + + +Topology diagram of the four-fibre MS shared protection ring. Nodes are arranged in a rectangle: G-A-B on the top row, F-E-D-C on the bottom row. Arrows indicate signal flow. Annotations show: T1 SF-R at node E; T2 SF-R and T3 SF-R clears at node B. A legend indicates 'T1533980-99'. + +**Figure I.9/G.841 – Four-fibre MS shared protection ring – Unidirectional SF-R plus unidirectional SF-R on non-adjacent spans** + + + +**Legend:** + +- Node sourcing K1 and K2 +- Node in full pass-through, K1, K2 and protection channels +- % Drop part-time traffic at intermediate nodes + +**K1 K2 Signal States:** + +| Signal Type | K1 | K2 | +|-------------|-----------|----| +| SF-R/E | F/S/RDI | | +| SF-R/E | E/L/IDLE | | +| RR-R/E | F/S/IDLE | | +| SF-R/E | E/L/IDLE | | +| RR-R/E | E/S/Br&Sw | | +| SF-R/F | E/L/Br&Sw | | +| SF-R/E | F/S/RDI | | +| SF-R/E | F/L/Br&Sw | | +| SF-R/B | C/S/RDI | | +| SF-R/B | C/L/Br&Sw | | +| RR-R/C | B/S/Br&Sw | | +| SF-R/C | B/L/Br&Sw | | +| SF-R/B | C/L/IDLE | | +| RR-R/C | B/S/IDLE | | +| SF-R/C | B/L/IDLE | | + +**Timing Events:** + +- T1:** SF-R failure detection at node C (S-P #2a(2)). +- T2:** SF-R failure detection at node B (S-P #3 (Annex A)). Switching occurs at nodes B, C, and D. +- T3:** SF-R failure clears at node C (S-P #1e (Annex A)). Node E performs a full pass-through (S-P #1f (Annex A)). Node F has no action (S #5). + +**Network Diagram:** + +``` + + graph TD + A[A] <--> B[B] + B <--> C[C] + C <--> D[D] + D <--> E[E] + E <--> F[F] + F <--> G[G] + G <--> A[A] + + %% Failure indicators + E -- XX --> F + B -- XX --> C + +``` + +T1533990-99 + +Timing diagram for a four-fibre MS shared protection ring. The diagram shows signal paths across nodes A through G over time, with specific switching events at T1, T2, and T3. A table on the right lists K1 and K2 signal states for various fibre types (SF-R/E, RR-R/E, SF-R/B, RR-R/C) categorized into 'First ring SF' and 'Second ring SF'. A legend at the bottom left explains the symbols for node sourcing, full pass-through, and dropping traffic. A small network diagram at the bottom right shows the physical layout of nodes A-G with failure indicators (XX) on the T1 and T2 links. + +Figure I.10/G.841 – Four-fibre MS shared protection ring – Unidirectional SF-R plus unidirectional SF-R on non-adjacent spans (transoceanic application) + + + +**Legend:** + +- Node sourcing K1 and K2 +- Node in full pass-through (bidirectional); K1, K2 and protection channels +- - -> Node in full pass-through (unidirectional) + +**NOTE – See Tables 7-7 and 7-8 for bytes K1 and K2 formats.** + +**Signal State Tables:** + +| T 0 – Idle | | | +|-----------------------|------|--------| +| 1a | NR/B | A/S/ET | +| 1b | NR/G | A/S/ET | +| 2a | NR/C | B/S/ET | +| 2b | NR/A | B/S/ET | +| 3a | NR/D | C/S/ET | +| 3b | NR/B | C/S/ET | +| 4a | NR/E | D/S/ET | +| 4b | NR/C | D/S/ET | +| 5a | NR/F | E/S/ET | +| 5b | NR/D | E/S/ET | +| 6a | NR/G | F/S/ET | +| 6b | NR/E | F/S/ET | +| 7a | NR/A | G/S/ET | +| 7b | NR/F | G/S/ET | + +| T 1 – Node fails | | | +|-----------------------------|--------|-----------| +| 1c | NR/G | A/S/IDLE | +| 2c | NR/A | B/S/IDLE | +| 3c | NR/D | C/S/IDLE | +| 4c | NR/E | D/S/IDLE | +| 8a | SF-R/F | E/S/RDI | +| 8b | SF-R/F | E/L/IDLE | +| 9a | SF-R/F | G/S/RDI | +| 9b | SF-R/F | G/L/IDLE | +| 10b | SF-R/F | E/L/Br&Sw | +| 11b | SF-R/F | G/L/Br&Sw | + +| T 2 – Node repaired | | | +|--------------------------------|------|-------------------| +| D | ---- | /0000 0000/-/---- | + +**Default APS Code Format:** + D [K1 ID] [K2 ID] [Remaining bits] + Default APS codes are defined as having K1 ID value = K2 ID value with the remaining bits = don't care + +Sequence diagram of a four-fibre MS shared protection ring showing a node failure and recovery. The diagram tracks signals across nodes A through G and back to A over time. It includes phases for idle state, node failure (Node F), and node repair. Signal states are shown in tables on the right, detailing K1 and K2 byte values for various channels (1a-7b, 1c-11b). + + + +Topology diagram showing a ring of nodes A, B, C, D, E, F, G. Node F is marked as 'T1 Node Failure'. Arrows indicate signal flow between nodes, showing that signals from nodes E and G do not change until they receive non-default APS codes. + +Signalling from nodes E and G does not change until they receive non-default APS codes + Default APS codes are defined as having K1 ID value = K2 ID value with the remaining bits = don't care + +**Figure I.11/G.841 – Four-fibre MS shared protection ring – Node failure on a ring with extra traffic** + + + +**Legend:** + +- Node sourcing K1 and K2 +- Node in pass-through (bidirectional); K1, K2 and protection channels +- - -> Node in K-byte pass-through + +**Byte Format Tables:** + +**T1 – RING SF** + +| | | | +|----|--------|-----------| +| 1a | RR-R/D | C/S/Br&Sw | +| 1b | SF-R/D | C/L/Br&Sw | +| 2a | SF-R/C | D/L/Br&Sw | +| 2b | SF-R/C | D/S/RDI | + +**T2 – SPAN SF** + +| | | | +|----|--------|-----------| +| 3a | SF-S/D | E/L/IDLE | +| 3b | SF-S/D | E/S/IDLE | +| 4a | RR-S/E | D/S/Br | +| 4b | SF-P/C | D/S/RDI | +| 5a | SF-S/D | E/L/Br&Sw | +| 5b | SF-S/D | E/S/Br&Sw | +| 6a | RR-S/D | C/S/IDLE | +| 6b | SF-P/D | C/L/IDLE | +| 7a | RR-S/E | D/S/Br&Sw | + +**T2 – SPAN SF clears** + +| | | | +|-----|--------|-----------| +| 8a | SF-R/C | D/L/IDLE | +| 9a | RR-R/D | C/S/IDLE | +| 9b | SF-R/D | C/L/IDLE | +| 10a | WTR/D | E/L/Br&Sw | +| 10b | WTR/D | E/S/Br&Sw | + +**Timeline:** + +- T1:** Initial state. Node E detects SF on working only. +- T2:** SF-S detected at node E. Nodes B, C, D, E, F, G, A transition through various states (Drop ring, Enter span switching state, Span Br & Sw, K-byte pass-through). Node E enters WTR. +- T3:** Span SF clears at node E. Nodes transition through states like Enter ring switching state, Bidir full pass-through, Ring Br & Sw. Node E signals ring SF. + +**NOTE – See Tables 7-7 and 7-8 for byte K1 and K2 formats. SF-P and LP-S use the same code.** + +**Summary Diagram:** + +Nodes: G, A, B, F, E, D, C. Arrows indicate traffic flow. Labels: T2 SF-S, T3 SF-S clears, T1 SF-R. + +Sequence diagram of a four-fibre MS shared protection ring showing SF-S and SF-R detection and clearing across nodes A through G over time T1, T2, and T3. The diagram includes state transitions for nodes and a list of byte formats for K1 and K2. + +**Figure I.12/G.841 – Four-fibre MS shared protection ring – Unidirectional SF-S pre-empting a unidirectional SF-R on adjacent spans – SF-S and SF-R detected on adjacent nodes** + +# APPENDIX II + +## Generalized squelching logic + +This appendix provides the generalized squelching logic for circuits that are not of a simple bidirectional nature. Generalized squelching logic can be derived from the notions of squelching for basic unidirectional circuits, squelching for multiply dropped unidirectional circuits, and squelching for multiply sourced unidirectional circuits. Bidirectional switching and the multiplex section shared protection ring switching protocols described in other portions of this Recommendation are not impacted by this generalization. The extension of squelching logic formally allows a greater variety of services to be provisioned within the context of this Recommendation. + +For clarity, the squelching requirements of this appendix will be discussed from the standpoint of an observer at a switching node. For simplicity, the figures show just the switching node on one side of the node failure. + +## II.1 Squelching for unidirectional (and bidirectional) circuits + +The following two rules are required for squelching simple unidirectional circuits: + +- 1) Assume, with respect to the switching node, that the failure is in the direction of the unidirectional circuit. Squelch the circuit (insert AIS into the circuit's corresponding protection channel as it is bridged in the direction away from the failure) if and only if the node failure scenario includes the exit node for the unidirectional circuit. See Figure II.1. +- 2) Assume, with respect to the switching node, that the failure is in the opposite direction from the direction of the unidirectional circuit. Squelch the circuit (insert AIS into the working channel) if and only if the node failure scenario includes the entry node for the unidirectional circuit. See Figure II.2. + +Note that the combination of these two rules give the current rule for bidirectional squelching of a bidirectional circuit at a switching node if the circuit is terminated at a failed node. See Figure II.3. + +## II.2 Squelching of multiply dropped and multiply sourced unidirectional circuits + +### II.2.1 Multiply dropped unidirectional circuits + +A multiply dropped unidirectional circuit is shown in Figure II.4. Intuitively, in the presence of failures, the squelching logic should allow a circuit to be delivered to as many drops as possible. The corresponding squelching rules are similar to those for simple unidirectional circuits: + +- 1) Assume, with respect to the switching node, that the failure is in the direction of the multiply dropped unidirectional circuit. Squelch the circuit (insert AIS into the circuit's corresponding protection channel as it is bridged in the direction away from the failure) if and only if the node failure scenario includes the exit node for the multiply dropped unidirectional circuit. See Figure II.5. +- 2) Assume, with respect to the switching node, that the failure is in the opposite direction from the direction from the multiply dropped unidirectional circuit. Squelch the circuit (insert AIS into the working channel) if and only if the node failure scenario includes the entry node for the multiply dropped unidirectional circuit. See Figure II.6. + +A unidirectional broadcast is treated as two independent unidirectional circuits for squelching purposes. + +### II.2.2 Multiply sourced unidirectional circuits + +A multiply sourced unidirectional circuit is illustrated in Figure II.7. The following discussion is independent of which source is actually transmitted to the end node, or how that decision is made or implemented. The objective of the squelching logic is, in the presence of failures, to deliver the circuit to the drop node as long there is at least one source. The corresponding squelching rules are similar to those for simple unidirectional circuits: + +- 1) Assume, with respect to the switch node, that the failure is in the direction of the multiply sourced unidirectional circuit. Squelch the circuit (insert AIS into the circuit's corresponding protection channel as it is bridged in the direction away from the failure) if and only if the node failure scenario includes the exit node for the multiply sourced unidirectional circuit. See Figure II.8. +- 2) Assume, with respect to the switching node, that the failure is in the opposite direction from the direction of the multiply sourced unidirectional circuit. Squelch the circuit (insert AIS into the working channel) if and only if the node failure scenario includes the entry node (i.e. the first source node) for the multiply sourced unidirectional circuit. See Figure II.9. + +### II.2.3 Application to ring interworking + +For the ring interworking described in Recommendation G.842, the bidirectional interworking circuit is a multiply dropped circuit with two drops (drop and continue), and is a multiply sourced circuit with two sources in the other direction. The squelching for ring interworking is precisely the combination of the squelching for multiply dropped and multiply sourced circuits given above. More generally, the squelching rules discussed here extend to unidirectional circuits with combinations of multiple drops, multiple sources, or multiple broadcasts. + + + +X Node failure +| Switching node + +T1529690-98 + +Figure II.1/G.841: Two ring diagrams illustrating unidirectional circuit squelching. The left ring shows a failure (X) at a switching node (circle with a line) where the failure is in the direction of the unidirectional circuit, resulting in 'do not squelch'. The right ring shows a failure (X) at a switching node (circle with a line) where the failure is in the opposite direction, resulting in 'squelch'. A legend indicates that an 'X' represents a node failure and a vertical line represents a switching node. The text 'T1529690-98' is in the bottom right corner. + +**Figure II.1/G.841 – Unidirectional circuit squelching example where the failure is in the direction of the unidirectional circuit** + + + +X Node failure +| Switching node + +T1529700-98 + +Two diagrams of a unidirectional ring network. The left diagram shows a failure at the bottom-left node, with the adjacent switching node labeled 'do not squelch'. The right diagram shows a failure at the top-left node, with the adjacent switching node labeled 'squelch'. A legend indicates that an 'X' represents a node failure and a vertical line represents a switching node. The code T1529700-98 is present. + +**Figure II.2/G.841 – Unidirectional circuit squelching example where the failure is in the opposite direction from the unidirectional circuit** + + + +X Node failure +| Switching node + +T1529710-98 + +Two diagrams of a bidirectional ring network. The left diagram shows a failure at the bottom node, with the adjacent switching node labeled 'do not squelch'. The right diagram shows a failure at the top-right node, with the adjacent switching node labeled 'squelch'. A legend indicates that an 'X' represents a node failure and a vertical line represents a switching node. The code T1529710-98 is present. + +**Figure II.3/G.841 – Bidirectional circuit squelching example** + + + +Figure II.4/G.841: A hexagonal network diagram showing a multiply dropped unidirectional circuit. The nodes are arranged in a hexagon. Some nodes have arrows pointing outwards, indicating traffic leaving the network. A label 'T1529720-98' is present at the bottom right of the diagram. + +**Figure II.4/G.841 – Multiply dropped unidirectional circuit example** + + + +Figure II.5/G.841: Two hexagonal network diagrams illustrating squelching behavior. The left diagram shows a failure node (marked with an X) where traffic is not squelched, labeled 'do not squelch'. The right diagram shows a failure node where traffic is squelched, labeled 'squelch'. A legend at the bottom left defines the symbols: 'X Node failure' and '| Switching node'. A label 'T1529730-98' is present at the bottom right of the diagrams. + +**Figure II.5/G.841 – Multiply dropped unidirectional circuit squelching example where the failure is in the direction of the unidirectional circuit** + + + +X Node failure +Switching node + +T1529740-98 + +Two diagrams of a hexagonal network. The left diagram shows a node failure (X) at the bottom-left, with a label 'do not squelch'. The right diagram shows the same failure but with a label 'squelch'. A legend indicates 'X Node failure' and 'Switching node' (represented by a circle with an arrow). + +**Figure II.6/G.841 – Multiply dropped unidirectional circuit squelching example where the failure is in the opposite direction from the unidirectional circuit** + + + +T1529750-98 + +A diagram of a hexagonal network with multiple sources. Arrows point into the network at three nodes: top-left, top-right, and bottom. Other nodes have arrows pointing out of the network. + +**Figure II.7/G.841 – Multiply sourced unidirectional circuit example** + + + +do not squelch + +squelch + +X Node failure +| Switching node + +T1529760-98 + +Two diagrams of a hexagonal network illustrating squelching when a failure is in the direction of the unidirectional circuit. The left diagram shows a failure at the bottom node with 'do not squelch' text. The right diagram shows a failure at the right node with 'squelch' text. A legend indicates 'X' for node failure and '|' for switching node. Reference T1529760-98 is present. + +**Figure II.8/G.841 – Multiply sourced unidirectional circuit squelching example where the failure is in the direction of the unidirectional circuit** + + + +do not squelch + +squelch + +X Node failure +| Switching node + +T1529770-98 + +Two diagrams of a hexagonal network illustrating squelching when a failure is in the opposite direction from the unidirectional circuit. The left diagram shows a failure at the bottom-left node with 'do not squelch' text. The right diagram shows a failure at the top-left node with 'squelch' text. A legend indicates 'X' for node failure and '|' for switching node. Reference T1529770-98 is present. + +**Figure II.9/G.841 – Multiply sourced unidirectional circuit squelching example where the failure is in the opposite direction from the unidirectional circuit** + +# 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 Programming languages \ No newline at end of file diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92e2ad596d9f216bcda8ccd82786bc1f01dc786f --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb56b0f0f9050d6fcbe5cd65c419fc9254b56e95da310f22a68ab3eb391e9ee3 +size 93020 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa6880d0afff17ea6d5c5a075f13f1706e53cbff --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80bae64f58d381146500b87d65723a01135088f8245798f7020f908beb942571 +size 13935 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a5079c341fa7d661b7872648730a7bdce77fc86 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdcdad68f0a5822f0c83e0f75f503d2d2724178ea95f399252eb8a9002063818 +size 21971 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50f22b32ccf1c0fa0bffcef4e71d1714c043c591 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:deaccd1b271ad4cbb8f6988d6939038c70b810730020f4a7242d50afac9549e2 +size 11522 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ead3a4b9748cfb79664a2040eac1b693d691522e --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:636197eec727cd8ed957b3626ab96c8797e71d94b1c837a9ea717c600e411bf2 +size 27011 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5c5e790a97aa72529a6ba7b50cda83db081f5c4 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fa9e5aa23da6c146801ce53ea60fbb898fbf85d3a77f569e7d857a9be0ecd9c +size 26964 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/15e4a144a88176b71ea3eff2722253b0_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/15e4a144a88176b71ea3eff2722253b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66fd3ff58d2648c042b99ddea2c181235ac822f7 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/15e4a144a88176b71ea3eff2722253b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:558d4f7bf6c402c489254f7144353897ec5c8c9f5532407381cf3a55794c393f +size 11792 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6d78958c669b67553f17157545dd305f2fb87d4 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45795c7e13a91eeb3735001f25a9446f0c5cdd3253e81b13004f5a1cb7b02f18 +size 18085 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86ff39a1f5f3228f91df933f64a766d17a18bcdb --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5954df277f71ec39fe338d0e4d2d830615da8043c144b9e138322f57a27debe +size 55647 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/2de714cedbbdd36f901f71bafa78f75a_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/2de714cedbbdd36f901f71bafa78f75a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ee44ac9d137510a7915e2ca7988de2c1ffd570f --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/2de714cedbbdd36f901f71bafa78f75a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d993178a2c3b7ba32c9073ad4b8af01bd04d08a82b05429ab783ccd4b5c37a1 +size 12897 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae +size 8196 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..645d8c551290df689992eea6e694cc227c13daef --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1981731c00ae5d914a66a315c08c983f366533d763125e14dc2141b25d5d61c5 +size 69001 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4eb2b8c5b1ba03075410d5d56570598020a53c15 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e55f250342d0f6c047a42851240323a8a1f8ecfdbc4c53f4baf63c79596944b +size 32641 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd4dab101d921c2ade33b3d8db6f4bcb9a20855c --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d8c72d02e429bfd2684280e8edbc3ee32868a70cfd20b9fea137141506be428 +size 17372 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c43896d982c9c02e8494730e708851c3fe5fb470 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9baf4032d5b2ec8580df7461e7b636afce95b1c7c45b81b4beb00d07c79edd40 +size 12103 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ed3ff4b25fad678881316b94d6b9c6a87b8a0f2 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66d093d275c583e72e92a2af6186831daaba4595be1c5483a7ab43c0ab9a11eb +size 22218 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d3c48ed3e7d84386992e4006ac214710b4fcf88 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73affed007813ac25f2cf867eb2bcffa5160fbe9c5c950084b20d728c0f79eac +size 17007 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23fc8ea8d3c6da547caabcc78b795f87f84ef73c --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6e8c5cb7b3155601bb94029586c57d3790249e9057cf65e3a00f270e553590a +size 13237 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..578f8ea4361164fba2be715b2f3152273646a2b7 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b577114b8d665cd85e19c46c7fc6b33537203b44a338793d1c0506fde1c7c94a +size 8099 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3299ed35fa6ab3e19974e79e5143bcee1b90cf3 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91ded95b6b992cec3f5db308aa776aa5bfffeef8d6fe1ccbd7d38c9608ab39ee +size 12425 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dde754aa20e5021978738151c914a655038cf89 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2af710ca2b465ce5fb5bcad1588bebad4f81a4b76344a81314caeb9202984d3 +size 14815 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1417f6868ee2256ff8a9ed13cc3455e4127e04d --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e0241634bffc8c5e4cde09491c4e47b39cb422996182880d5e53eae2ba26d5e +size 138979 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29b43f4100ac9ac748f4fdc6a78eca01ced3456c --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5c504aa2c8c466fa1f5effeeee10dd62c915150c4c8abc9dbcd5e99d37cd8c3 +size 19461 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0659b563a109ff46ea71f3cff64a5a0ddd2b180f --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/73b5cce955ba9415a98791db7b0080ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d458bea49efcd7e02373595fe7bff3d0fca86af4127bafb352df97672b52a92 +size 37719 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9657a352bce59ce830f17a774d738f29e6465837 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88a2d2ba81dd613bec156f4c04d4d53e836da8e56a48e97cf475224fb2e24d95 +size 45424 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4e17e2c2913aa6ca8e21f00320842a21268b8be --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cfc70fd41b146ca2f4a80c9704cbfc759ffff4ca734c9c7154956ec0790bd37 +size 20265 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4496ac651b0394f95acbbc96ec1af7d2b2dde88 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:319d9f857b9a390c36d5164db6023096e677b373adaf954860d52fb5d037a24a +size 11462 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da0cd3d21f2748a7378510438d4df84a90cb6852 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02426f6a65c53d4f0fbef2bc50fd84387340d23771ba378052b4761f6d20060c +size 10253 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ebb43f3e70580da1d1d031a632b857aa8b83185 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41d3c4f6a7ee912f8aa27f33fa6fea4df403447dafb6d587be9f1e42e2f791e5 +size 25637 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fb2f58b1b12ef0e98501a95817ef0b75ad3af1a --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffac3acc30650cacfe993040ce71dce9e6f446bcea0337602828535c38faef1b +size 23041 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8825d42937311924153ea6cfb268ecb8cf58a4c --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3436e930de2af1c664648bf04d6b97a1791a10197506715f5476468def397c2f +size 29021 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..847e83e94b3448dd3f4c3cdd19f9c5e873d95a10 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ebd361fffef4027ed368ed1bacb0d34d03508b6360b225e874b9d266628ba3e +size 13767 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52e668eb7165b3eb790b6c36831776a910f528a8 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ecb45dd34a22f41dea3e717c44ee15697010c27be9e8b590da782fb0ae52300 +size 23357 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4047e85c72b08428b654e4d9be4ad54300bb3b68 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f095e232b4c30e3c89cedc7e34e638dd4df5e4f41101dda9f11b439941d7b6d1 +size 20951 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daf83b6d44eb0a582aad071eb4a30238b0fa533c --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8ee35e82023dcb035b4419e9467b7de06b242b57852bc714224103fa743d4e7 +size 37372 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..783aa7c2a3c079e9794608e8d7b3b79d055e61a1 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f312686e83c7f35698f013ab5fa9644fe1257ef891a7d75a37753a9a25c6ff3 +size 17477 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ebd52ac59ccdb9bd778398fd9a6fca4929587c8 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9270588eb53f8905a9fc0a71931e8e3096447707a3e5e3e855d09662d7d9ede +size 27806 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf6d52744b91a19bc53933466fd289fdf0ff692e --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb8e2240e5dce2ddda1030dace0b82ac9571b3844744bab53034154ed3e21cfb +size 17323 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af6c230ab1b1602e42bc71da3120c92eb4aafb8e --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8288a7a88892c452ee4291dfcac9ee27f593634b44f3f2bef9afb3da33806c37 +size 67994 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34a2ea76d42551894c493b3eb5abe1267bc07169 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1401081d47b59536724ab616f013252c7a295fe58d957ced3d2c6f8b35e75fe0 +size 12694 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/dc23d430e878eb71b8cd589984113940_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/dc23d430e878eb71b8cd589984113940_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aecc50e5189ceb8f66902ac013230ab1c19df6dd --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/dc23d430e878eb71b8cd589984113940_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e91a870dcfa69b1686eff26c1fa063a71cb2f3dbbd4bc99cd9826f43b11bfb5 +size 14052 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efd5d24dd7944a83d4cbbd782d5732f2b905d77a --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f80e1662e429f3f5ec45740a91f7cfcb90104deccf27f09c3152baee15a09328 +size 11085 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..836147da9ed7f7bda9500490849284cb6893fdf3 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:223b175494431adf1d5dacab439dcc7aa5b119d19e008c2ea02348116832d363 +size 117971 diff --git a/marked/G/T-REC-G.852.2-199903-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/G/T-REC-G.852.2-199903-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e86932fcc005a90d94378ee1fad2d5091965c25 --- /dev/null +++ b/marked/G/T-REC-G.852.2-199903-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb6670825a2b12cf20ebf0441a1a6671b6196e206a28e4d29a91c3f2d23432db +size 106295 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..492b353e888e37d06b10eba36b28ba2486f3d793 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06ecba9dcdb0dbbcc3d28e89b1b7644455440f6b22fa41aed92d9ab3be7879ce +size 17995 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/0ccaa59b5bc46884777e728ee3dadaa7_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/0ccaa59b5bc46884777e728ee3dadaa7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e85b60d6abe54995e147a58d0761b3cddcdaf47 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/0ccaa59b5bc46884777e728ee3dadaa7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d4d6889b30ad8dd9102d4baaf3a346205e9c4c140b3f31a384c149f2adc4465 +size 9293 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/155cdc51eb4f6a3e9f032459d85a2f77_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/155cdc51eb4f6a3e9f032459d85a2f77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32f018a8d0f8be1b361a639b265d57bc2deaae2e --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/155cdc51eb4f6a3e9f032459d85a2f77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79e5dd0ee8f2f89e82f2e865423574fb39a2d6fab04b9f45c4c73cbe2467cd32 +size 21831 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/18e519d1f91133e080347562f681dfb5_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/18e519d1f91133e080347562f681dfb5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97ceb7cf26d1d5746b702d9569499120592ec7e0 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/18e519d1f91133e080347562f681dfb5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b593917876beacb23a1c5c465705f6700ad626950f886456d7cda2c3c844dac +size 34914 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/1d7843cba3689033fb3d36d56984cf38_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/1d7843cba3689033fb3d36d56984cf38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bde905fd3d1a2e5dd87bbd4473d12a6d2f40a39c --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/1d7843cba3689033fb3d36d56984cf38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cbd05c7584037d18c586a727af592b369081adcda9f2df072b508d2ee45a946 +size 21721 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/22f69a5473360beb672a10970dbcfa30_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/22f69a5473360beb672a10970dbcfa30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c34679db25f94f5520b8d844deddd0a1ff88c632 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/22f69a5473360beb672a10970dbcfa30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e02de5424809ea6f127dd9735669bda7c31908336cc932749ea7f60ea6f472f9 +size 38521 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/24a89bcaba787f2bc1721356480a4a01_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/24a89bcaba787f2bc1721356480a4a01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc56a83df77f33e37ccb892dc04a9fa37617f0c7 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/24a89bcaba787f2bc1721356480a4a01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2986430afbcdfd817dfd69992e20d88077d8d470de9ab566a7692ab80835289 +size 20622 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/255efa1d461fc79b4ed367aaec11637f_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/255efa1d461fc79b4ed367aaec11637f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6c6668d025075dbf8fc90de3437512ae17885f2 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/255efa1d461fc79b4ed367aaec11637f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da754df2bd1736a14fc53b26e7ba1a1ae9d55c4254cc78c9debed6aaadb6aac0 +size 35847 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d222a7dd59683a1ac43f51ccd8c82d55b9342db --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1773abfc745f4c5ca6ef54cc1c2eab86ab22334d3c05c10e2d05a4a138938808 +size 75021 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc3e1343bb276ebffabd306f1dce718fa0121d2b --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61a9a6efb4ba192dd91373fabfbd115bdf63e41f09e63b35403dcfd7aabf4347 +size 21153 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae +size 8196 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/2dfd7b53bd3c518fc1f68921ed2bf441_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/2dfd7b53bd3c518fc1f68921ed2bf441_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15ba8073f14c9ecaa8d20d225219fe5487a6fb11 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/2dfd7b53bd3c518fc1f68921ed2bf441_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:754f277aae946099466ecd4e56b3235383014be0bcef4a4a9345ce6852db6059 +size 28484 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f890ef2b6de8cc7d0b62d2aeb5d748bb6bc87746 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b387fc8f363122c066c9d29e873d311f0868017fb5f7991c2d2fbc963dca5e81 +size 10164 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07f853139d014493e5f4f714178c06eee8e3c30d --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45f3231c0fd9f63404eac1b934eba5e958bf7b7516c1c11633b25302d4523a6c +size 34125 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/3493d7ba4c86f944e159de1bf45ff03d_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/3493d7ba4c86f944e159de1bf45ff03d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33c2b25b66df6a56b4686a5f4aa98fcf8488ddbb --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/3493d7ba4c86f944e159de1bf45ff03d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd972647334052d40f05daee35f15f7dcd1e8f8a73bf3bd704aaa6cfc9ed9c4e +size 16827 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a40c3a89a27b47577cd312dbb84c801d89dc0522 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/3766b291e69420b0437ae278b057b5ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed719ca91721e6a7cae96e5096dfb0956a76c84b779e0f37bcde451a727f36e0 +size 71997 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2e00eba6374dc44181ff46cfb7eb0d1719e3d72 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91d0d6f6a651220258088a225260b4422116ad4a2c8b759a2b0a25f5c66ef1a8 +size 17674 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a35ba584bb46f8131ed284649f3f6c9266604b91 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0eaa731fdc0644774c91ab25c4d88b1c171460c499f642cfb5d1943ba1adce23 +size 9264 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/583e14835ddabad1d8b92a07b82fc31b_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/583e14835ddabad1d8b92a07b82fc31b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3ba7ec64d746e9b1623e201375d7d9e77b8c0a3 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/583e14835ddabad1d8b92a07b82fc31b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:202987c96c17cc406de366b8775f1d85a6253f20ec396ca630d6d9585ff6dd18 +size 14357 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/5a13c28486ba6b19f59d7a9a7a1c3f28_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/5a13c28486ba6b19f59d7a9a7a1c3f28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa39c6ff14744a2930aafc931a9f9ce8b410acab --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/5a13c28486ba6b19f59d7a9a7a1c3f28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7404b493043958c77fb1fde269975391ec6e451a8f2896078a7a09ebc707049 +size 13683 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6963e75d992a61f6a1a719251772120f82a913d --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5e59c4f426226928782be25d8701dc375ea2040841bf6304d2af744b6fb4d89 +size 16013 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a1512642ee490e5ebb5345c5b03ef52bce9b552 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcffd9625afbed3d65c33a7fc95a712819f9bc84e3ceb5ab97f622c8dbdee8f3 +size 12562 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ea13060630deea45db3205fed766c46f01deb1a --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2edd3e9db5e7d752bb533b009f279b404c1218fb54ada9bc3a6d99358079f31e +size 24431 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0586d6056b7ec1c06f6f7472e5665fbd44ce97dc --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:676df895fff4706a28d10a1eb747a90dd5778dd0c9c0d0371fcc1fc2aadc787f +size 19915 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f6fdbcf5d20874bb38fe0fcd119e4b76c92d1dd --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:291e92a4d9129191a809c356d5b7f51c26f7049233aea0d4275e89043536640c +size 76059 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93f84aab9ea3fe0323977cb156a924db6dcf3cab --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:717ed89c33293fba90db6f6aeb1fca622ad825f83cd9d7aa7d489d197cd4083f +size 30572 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/7ef15a55963eccd86906be784f1d75c4_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/7ef15a55963eccd86906be784f1d75c4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58f10ccd4ca30ebb26b482b59d359a733de48028 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/7ef15a55963eccd86906be784f1d75c4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6fb2d5d81bc70f0df715c824ccf1fff6c27b2d49227a93c8e919871ec989196 +size 16253 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..864384eb21fcc72b5ac81ab6e318c0aa2eb0a6e3 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d8e3632a026177fc96763066adda72f0c9d0288fab66b9da08c4d806b53e486 +size 10854 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/848073118eebfdbfdb9a60e3923fe0b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b81d7cb8250086a8c05c93f414f80219bdfbb91 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/848073118eebfdbfdb9a60e3923fe0b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d6a68137fb0fbbc72c08bdc7d5d90f35f873ebd1c1396c6fcbd4f3fe3d1ba80 +size 8426 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/85cd27423acb6a60da23ab5bf9086bd2_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/85cd27423acb6a60da23ab5bf9086bd2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..361c1bdda178a61e8dadf34dd1b840344d034656 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/85cd27423acb6a60da23ab5bf9086bd2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bb935ca14350073db97c6fd62f06b0d70d37e2727db63714a51ec0520999b33 +size 17841 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/8a9f4764511ce90622893ec65c065eeb_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/8a9f4764511ce90622893ec65c065eeb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a42024c0b72907d99fe33a23d63910997fe9705c --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/8a9f4764511ce90622893ec65c065eeb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:189317ca6296a785620541f8a522d772780bf5db6150215ca65546fb5d99ea53 +size 33969 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8ed93220dca73afe12881035d845c3c659c5ffd --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42c4e92987d53ec3e22c6595b16c70c564abdfc568f49eb9bd1b3ac83b8e5b37 +size 78921 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58c16525965d81829492e107e60d538df670656a --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13c006136e517004c7fa5161315e7b3cacca601ecc34813ca04d9550ee49243d +size 116091 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..217c735c6c480b735e5a21fc9356ea8eca526fff --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d31af43456412c2ead37f4efb0108ba27adf25b1679f1121de51a1dd37385985 +size 18838 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/a461c3fbcb754ea34add62bb4bd25751_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/a461c3fbcb754ea34add62bb4bd25751_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06ead7d993618474f8805d8d518d67b1fc7c4b40 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/a461c3fbcb754ea34add62bb4bd25751_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce3b4f873f7fb753e8b099f46b47dce8967634e004e37d022a2b871134e0ba7c +size 15050 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cf76ab72f47605482e7eb63e3a10308102a142e --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94b7b7d6f9c4d8871cb54011037919c3a193b93f5f4e5d11ccc5534209473082 +size 21663 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab68b3539a7ac288fe3b04ddd69ad9ecd663c772 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a2e3a1e37b0a19e21787d7ab51e79efe6d16d8edb02938d5454873ef654f819 +size 11863 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/a89d151b67109378baed0c117830cf78_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/a89d151b67109378baed0c117830cf78_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69e2e41defc6aaf4b420c77e0ec5f4e8104f440a --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/a89d151b67109378baed0c117830cf78_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5366bc4685d260087ded91b1b44c8e3c9584e9d9ed18f332fa0eeb88fddaf501 +size 34520 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a29d9d158a8af7b23d4a1da8f755aef7e2287d8 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6dae7a053ff827bbe971e8993bb5ea3e7ef4546c35d64c855ce091665935cc35 +size 50383 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ab46d327a46cf83e0dbbee171bca264e7d00766 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abc50c09517acc869f4123166af7af72b075f79ba6c6969c3509f7e0e9b404bd +size 23700 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/b2fb400fc9b21b9a4449b6460911b8b4_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/b2fb400fc9b21b9a4449b6460911b8b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d8697f5399584bd5cec2707ae15845b06f76a3e --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/b2fb400fc9b21b9a4449b6460911b8b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62175259ddb63138ffaeaad195d904ef3df776573f1c100252b94af810498b12 +size 22613 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73c2275e590f31f4cc186ccf588720a4c4c28293 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4ed7573a32dcda57495199d9da55f894435cfc8f94b98247f658c262525fce7 +size 9240 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/b5987d63203a5fa601921039922ac520_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/b5987d63203a5fa601921039922ac520_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7cdb42850148ef7dd1aa58e9fa8f75387a26fb5 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/b5987d63203a5fa601921039922ac520_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a32e4e4904e7463b6509be478cb90f4a67aa38d924a17489a819243423b8f34 +size 9003 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/bc9152f59fdf75ea4835a8a60f08bef4_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/bc9152f59fdf75ea4835a8a60f08bef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cfa382713a2da0b46f0773593d3e950cd29c5b8 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/bc9152f59fdf75ea4835a8a60f08bef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd59ec59eead54d40994fb5558b1236b65320d9a6724080bf8a6ff62042cb738 +size 20978 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/bdd19e1aefc189598ab515f8f12518dd_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/bdd19e1aefc189598ab515f8f12518dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbc1032056e57f778ec2fecc83f83feb6b5b7bf6 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/bdd19e1aefc189598ab515f8f12518dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff65c55b6a4d4263b494e8d2b71f1477fc780181e6398a73655c6964638afa41 +size 19852 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2a229c6321db06b6b35eaffad94cf089c73f381 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8baa3a0085eb1516c0d0cc7448a33829bf32c02c0579810f659ba83c56029e5 +size 16108 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/bf32ff2a1af507083217ccc56c515a50_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/bf32ff2a1af507083217ccc56c515a50_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3fefa00c4b5be4627c4ad00b5a85e9a7757f5c6 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/bf32ff2a1af507083217ccc56c515a50_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ab199bde4a429a258dffcf925026a8f36637d454a4db8abc6161568043ddaf7 +size 16834 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/c4312d6d416e683271db3162a4f009fc_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/c4312d6d416e683271db3162a4f009fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8354baf2ec3c5206d8c2a5dcb478ce5efb3216d4 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/c4312d6d416e683271db3162a4f009fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45fe474196362a3ff38d23bd7e13f4e9ce1e8bbedcd111032a764f6763cf9d68 +size 18198 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60c3143338b8b05fcf902057de8ec6e1b262ae10 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:491dc4815b29ac55e28e9117e14bc54f51688e95e9dbd13d2c98207dc157b465 +size 89126 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be197df7560a1f0a6f785c3916f802450c209319 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1200d46b17cf6001bd5d2dc95bd0dc19e93e179a3d7e14b3240e396a15fa4eba +size 43850 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/d99a54a2d327cbeae6f5a3abd0c978ad_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/d99a54a2d327cbeae6f5a3abd0c978ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e9cf925bd0646027781b4469e561342ba3be0bf --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/d99a54a2d327cbeae6f5a3abd0c978ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:471761c1b9774b0ac010a6b96d6ccb21d762622fb2b98a574681f8dd40a3e3fc +size 16842 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/db42f27db117c6e8ac41dbbb67722021_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/db42f27db117c6e8ac41dbbb67722021_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b70e318d67cd6c7f4e3aeff514f3a4a810cd3097 --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/db42f27db117c6e8ac41dbbb67722021_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c580bda1d3214d4bc509e8edd16221ee4bb8f3752b7ba3037504397d04ff419d +size 15991 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fda9f81ddc985960f9245f03df3acc51c4cdbbdf --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec6705f7b36429eccfd8e9112ade3aa6d645f19d13254735fed1f06f401fd3e9 +size 40663 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c717aafef610c11f9321a9a968e9679804db30a --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9ca0d84cacfc0f395acdb73a4933da54724ba25bc18c6cd02d0d97a9cb8a552 +size 13563 diff --git a/marked/G/T-REC-G.853.1-199903-I_PDF-E/f82372c6a14ee48b0d00b0e591f8c05b_img.jpg b/marked/G/T-REC-G.853.1-199903-I_PDF-E/f82372c6a14ee48b0d00b0e591f8c05b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a6fa8abcb6ab5ccc5c2b4c106237a7bd9ba0d7d --- /dev/null +++ b/marked/G/T-REC-G.853.1-199903-I_PDF-E/f82372c6a14ee48b0d00b0e591f8c05b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12c1035ee8d90544ef5dd8a1dfafafb6562c94c9124f9906797c2ea5286a067c +size 19550 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d589b18372b35bd468204ca6c188fbdb8c6618da --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79496ee83fa9b75d03a1900f84ae73f8e921353a80362257dab2bb61d65dcb2e +size 88084 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14cd8f12409ff467f886716a2d193e1c2656a5c6 --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f640056ae2ddb647eda3cbad20de92ca38e282067ec7d1d0f911b793a97e8896 +size 60316 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d4e56b2cc9bfe166cbba6ee4fc1d4b4bf978560 --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a614a74768236d17887368d09e7e812f55f8774145f978de67ed2ad30e25057 +size 78810 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e34ef6192008e5a6dd1330c8c938a1f7dd66ab4 --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/4af57aad638888edf2062306f8a54a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16eefdc46d51905f2990e397259cc45f761f5afd8e6fca1e76d366f53d272afb +size 82287 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/55136bc716146672fc680fa05989f1d2_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/55136bc716146672fc680fa05989f1d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87c7594908fb3f315a3dc5dc8eba1d30445490d5 --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/55136bc716146672fc680fa05989f1d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af6b2392663ecc9b46f4296b0b225c75a64938cac2b6d00669ca389a3b27d863 +size 29048 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcaecb9c5c3ae22288657d5424ebd79c3cb76a1d --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93ffedec451abf670649858d1a15aef5ef05d1d8305addf01c96ee7ba93714d7 +size 84084 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a798a68dc37fd85281eb31d490b17d00a3a0ce07 --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bb79cf8cc5a3f8215454108a8dd6b6d0900dea00f19b98fb0af31248c26ae63 +size 79349 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6044f1757a56a0c010f2baafb3c715c1e86ec0d --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0075b9a01a033c6c9fc14758aa2a9bdf41310e2e756532e367b76f9dc15b0c60 +size 46020 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42cd4d3c48ac36f05da1d7c3542762c44dfee295 --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50f4b425a701744685d79534b44aa5c4d2945f15f7a0495878ff62e772f87b12 +size 64826 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69187107276f00e2bb15afb2c9c83e61c49336fd --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be2cf3d58dbba90822c370261b9e71d788e9067feef918a880c7b82f2364c2a0 +size 98933 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13263f569fb0a1ea0c4d91bf40dc153d5b570818 --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e71a6537042ee808982cf59ff42f723dca446e6047af584452ab200f682871ec +size 158876 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-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.8601-200606-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59999299203124f7b570f60109901fb0da7d06d0 --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbcb8829a176fd6c1802b1df75b719c00b71b26b645c5d656621589f74607551 +size 149360 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..228fd612ca4b5039dcb8e80601d5eae5dd97611e --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4d5c0c80253fff96e630f929b457b9ff66cd6d6b1f48b44983129c39dd5f3a7 +size 181221 diff --git a/marked/G/T-REC-G.8601-200606-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/G/T-REC-G.8601-200606-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13f7d4f5361f855b8ea7b3b6005843f0f3eafaa6 --- /dev/null +++ b/marked/G/T-REC-G.8601-200606-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce45da5a52afc4da3b554df42be1a8a8ba0d523ffc7515fd287bb42e405210d1 +size 76478 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78d5ddabd5051d80533adc7b633831e3821d27e6 --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e76e097e164ed62b7b55d5ac0c3d83e9586a6ef9ee7f2af0c8c26a6eda416ae2 +size 40712 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f01f76be4585bb3ea614922415b04ef9175c41d --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97ee0cca8912708d02b53df8347062a50e0aeec6af05d6e23b4fec3cd7b20aad +size 132243 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8e71273292b67e7ce2a5b5d2132182ed3c1a742 --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80c87878fb57f4a7d7d4b8804c95d07eceb70438a7d490586bbce1229b462688 +size 67947 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/G/T-REC-G.975-200010-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.975-200010-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..640fa16c0938f90059b31daefd67d2cd15cac6a0 --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5400d278178ad8b9548aeb13a0d0dc7fcf5e4840226ab0b326d8ba010bc06f3 +size 80545 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00dc4f84e37b6bd6200e80610612bb1792ca9fb6 --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e7a08ea8fa697d400a1b5d3d91ed9d96511ff8e9ea307811a0b3386dc3d781c +size 39763 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/70f5f44cb855bbb0c203c00187b2113e_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/70f5f44cb855bbb0c203c00187b2113e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5a754a4834a39f0225368deddd207750ed44278 --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/70f5f44cb855bbb0c203c00187b2113e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57372b174a428dc757b994a231f4400aa503152cfdde4e3849bd039b0221f128 +size 25763 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..decde2b4eac5fcb8ba8511cc8de01e7540eb559e --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce4e117c75a32bd8f44078f84417bf863cbd8945e4fc049525f08c98f64d30f7 +size 85715 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d059e3d47cd736f9b00ad90f5f345bb1c07c9ce --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58bd9a4f63bd0cc06d2f2e41bcc1beae3aa169d3b3f6ddb162f505295c459514 +size 67009 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76bcfa86bb4b9212c5ddc841e2ce0909ec5ac420 --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f0df503c583f55749da51a8a1bb57d905f65a323bdca4376539bdacaed395b6 +size 26744 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b85267e9d9bbf7e2c23017335016bada2967d2b5 --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ed3e8fc24ee7a4b76d2aa0abdb214f02fd3d68068481acb9dfb121f56364bca +size 31219 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a838f6b63ee7e45452943c7f9e96ee03ec9c780 --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d33374f019bea56ef3abb9437d826cf130b676e3e00e6ebf5454cbd7485c1244 +size 69728 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..333eb8c47e47ca6cb266d5dfc47082a4d8646d80 --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5efb564de68e1f4cca7754b51d70fc071b3dfc127ac32b9135531e9f59501c1e +size 125114 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bd075f1144ee52a586df0df7276d1a2670aab36 --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03b0d805894e39a895c6712130c9e02fab2f46cf81f1e89421862cb7da53b7c5 +size 71265 diff --git a/marked/G/T-REC-G.975-200010-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg b/marked/G/T-REC-G.975-200010-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90d0772ba5128f7c486bb2ace1df00c4133a335f --- /dev/null +++ b/marked/G/T-REC-G.975-200010-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d41f6a35c0e316624ab8aa3f9c1bf2b4cd65e5df59d3e1a4676629763138379 +size 28365 diff --git a/marked/G/T-REC-G.977-201501-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.977-201501-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd85c5f0cf29767d5fce2cdb865aece52387c01d --- /dev/null +++ b/marked/G/T-REC-G.977-201501-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09082581f21d9548df66739aba3c0950a4cd19b319365b8f1c69a3129a386b3c +size 4070 diff --git a/marked/G/T-REC-G.977-201501-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.977-201501-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f83cb2c75a05a9d64d10386bed4d51fbf28277ef --- /dev/null +++ b/marked/G/T-REC-G.977-201501-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd2813fa231b2af57f74ef0a6085d6016e4c04762d0e26b981739be7b8ac6c47 +size 39721 diff --git a/marked/G/T-REC-G.977-201501-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg b/marked/G/T-REC-G.977-201501-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..079e4267535b1f9754f11ca89c503a1ca05f7bdf --- /dev/null +++ b/marked/G/T-REC-G.977-201501-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a1be2fac2ca3e0c5761e06ed91b9c08a13951ec876523d718edeeddea68e514 +size 32349 diff --git a/marked/G/T-REC-G.977-201501-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/G/T-REC-G.977-201501-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ce3057aa543d31cdacc18b06b78d07ae58df5fe --- /dev/null +++ b/marked/G/T-REC-G.977-201501-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ca6d9a4bcab0d7aad1c1dfba233db8ac27806755e5fcdb379c70195ab588018 +size 132318 diff --git a/marked/G/T-REC-G.977-201501-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.977-201501-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8a197114578115945891e02e4eaa525c2508ebd --- /dev/null +++ b/marked/G/T-REC-G.977-201501-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b331d9009796a558b800d03d5cf80481d4631480109de770281d832d612a8238 +size 28752 diff --git a/marked/G/T-REC-G.977-201501-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/G/T-REC-G.977-201501-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45d07e503ecce6a271e326483a752208421b4e41 --- /dev/null +++ b/marked/G/T-REC-G.977-201501-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac0925e6b9e3c6bfaa91f367986eb78f454c04df3a1b3047c6b1c30c4feb10e9 +size 40051 diff --git a/marked/G/T-REC-G.977-201501-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.977-201501-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2226b73f555f86c9e76f235eebca8a9e300b9b02 --- /dev/null +++ b/marked/G/T-REC-G.977-201501-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f61284f52828f4e2851aa359373ed26168a3cba18ac2c8548664f18ad49e616 +size 76388 diff --git a/marked/G/T-REC-G.977-201501-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/G/T-REC-G.977-201501-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a530ca6b6d18c0540683b1fc72596fcb4727d221 --- /dev/null +++ b/marked/G/T-REC-G.977-201501-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47b012221bac74a6866777c093555aadc0a2acff61a34d9477f0f17238865dcd +size 32796 diff --git a/marked/G/T-REC-G.977-201501-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/G/T-REC-G.977-201501-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5ed105b07ebda1c5fed9b88663a0d601f6a8dab --- /dev/null +++ b/marked/G/T-REC-G.977-201501-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:451d9f2780902e32e9ebb6b2e08c0f60d945bd58621f6a9e1287ea63498414cf +size 39253 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d +size 3828 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60fb4cf6c340aad42c17c8138173eab91fb20776 --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:016d127d524fd514763acad44aeaa60fddf0e2d4a949067882eb9f1768cf3a1d +size 70716 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..238dfbf3c323ad69e2ef7e2d74837330edde6a29 --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0adc689c84425afd48bb206b477b887c5ab485c30f90db17f1b6e052feb592b3 +size 32497 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..640e4b25a8bed9af074273ad093b138bcda21e76 --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7bc680322b86b23f8800100293eb17244802759a4a235e5bd158bf6c2278bd7 +size 107591 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41c55d66f06140351813b7364cb10d9e1c732f8d --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d971bb964667501d8512289b5a343794dbe858f1e3a903965d875430d4a82ba +size 106852 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82b3d46363725b6f4a535d2456acfb955641896d --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f654bbe3f010cd8f47b2343a8d2d66d5744b2cfdaf5fb06c11d362836ca9394 +size 134507 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6824340a6a25a19d7773db5e0a6c8dc863d47813 --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3deef872049240fcf3c7da890c382fa9dc99f016fca22fea01f9b8dec21056b0 +size 37096 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6fde14312618dce3ee18c622f94c60dda953db0 --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ce16df6d494c3405f58efd1e15af4119ad0d143b5427d11a87adfa5291a6a81 +size 22571 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9aacf4c3a7342ac20ba4a6c01eeb2d77a9c2d03e --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f50753575c0e085d9a8e932263907424857b1cf05d9e218c046aeb13a8f51cd3 +size 78776 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb40edf4fff2135fcbdf68b7437b8634b0c417dd --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fbadee65c51d85eed784702c6f3ef2a377aa0927f4e3408aed5a2daf61a1ae1 +size 13674 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d454413bdbed938d549b8775c6200c0c62e9a5c6 --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82cfa93f7092db65f1615634e3ad4113e60dcf50ff65c3b0fcb6c1c6b4742486 +size 58290 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fba302066fabe24343b0bdccbd0e6e5e9bbc16a8 --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60ac72f4fc8d257bd68cb05489aa3f23fef8e97ee418cc981cf7d63d8b57f04b +size 111535 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b937e5c671045d870e0592f353bc486f1224b860 --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8c53320d5c89a181b2023425c3575b366ccb61d64f1064d2f2507e989025468 +size 68342 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d737b5364fd18606491b79c216b85fea94ac0cf --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ff1783467bc448f1daf50634578aa0c4f625d51f4bd330f893fa47805c30c38 +size 136561 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db44b641afa58531fcc85169961a761b36fe9f5b --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:094fac95afb9f1f1bcde37efe61eafed4a9f0033f8ea855695c59f59a1df623c +size 116407 diff --git a/marked/G/T-REC-G.9802-201504-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.9802-201504-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1529f2b5b9a62dac11cccc1e3ec2bdfaa77a30ae --- /dev/null +++ b/marked/G/T-REC-G.9802-201504-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed80899258853e4fc75c30ad85df3c7723d892d3999908414f2fb884f7fb468e +size 114971 diff --git a/marked/G/T-REC-G.9802.2-202307-I_PDF-E/raw.md b/marked/G/T-REC-G.9802.2-202307-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e6b94b34a9cc6868026152f03af2603b4fb33861 --- /dev/null +++ b/marked/G/T-REC-G.9802.2-202307-I_PDF-E/raw.md @@ -0,0 +1,2651 @@ + + +# Recommendation**ITU-T G.9802.2 (07/2023)** + +SERIES G: Transmission systems and media, digital systems and networks + +Access networks – Optical line systems for local and access networks + +--- + +### **Wavelength division multiplexed passive optical networks (WDM PON): physical media dependent (PMD) layer and transmission convergence (TC) layer specifications** + + + +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 | +| 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 | +| Metallic access networks | G.9700-G.9799 | +| Optical line systems for local and access networks | G.9800-G.9899 | +| In premises networks | G.9900-G.9999 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T G.9802.2 + +# Wavelength division multiplexed passive optical networks (WDM PON): physical media dependent (PMD) layer and transmission convergence (TC) layer specifications + +## Summary + +Recommendation ITU-T G.9802.2 describes a wavelength routed optical distribution network (WR-ODN) based wavelength division multiplexed passive optical network (WDM PON). + +This Recommendation, as part of the multiple-wavelength passive optical network (MW-PON) ITU-T G.9802 series Recommendations, specifies a PON system utilizing a wavelength multiplexer in the optical distribution network (ODN). + +The specifications of both the physical media dependent (PMD) and transmission convergence (TC) layers of WR-ODN based WDM PON are captured in this Recommendation. + +The PMD layer specification includes aspects such as the reference logical architecture, wavelength plan, optical path loss, transmitter and receiver specifications, compatible ODN, etc. + +The TC layer specification includes the details of the forward error correction (FEC) code, implementation methods of the management channel, management functions, a set of processes and messages, etc. to provide similar operation experience as legacy PON systems, e.g., silent start and capability to map a local physical layer operation, administration and maintenance (PLOAM) channel. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.9802.2 | 2023-07-22 | 15 | 11.1002/1000/15548 | + +## Keywords + +PMD, TC, WRP. + +--- + +\* To access the Recommendation, type the URL
Privacy and security
Synchronization
Management capabilities | +| | Physical medium dependent (PMD) layer | | Electrical/optical adaptation
Wavelength division multiplexing
Fibre connection | + +## Annex A + +## Physical media dependent layer specification + +(This annex forms an integral part of this Recommendation.) + +This annex describes the physical media dependent layer specification of WR-ODN based WDM PON. + +### A.1 Physical media dependent layer overview + +This Annex includes comprehensive physical media dependent (PMD) layer specifications of WR-ODN based WDM PON. + +The structure and text of PtP WDM PON PMD from [ITU-T G.989.2] are partly retained. The general characteristics of PMD layer such as reference architecture, operating wavelength channels, line rate options, OPL classes and optical interface parameters are captured in this annex. + +#### A.1.1 Physical media and transmission method + +##### A.1.1.1 Transmission medium + +This Recommendation is based on the fibre described in [ITU-T G.652]. Other fibre types compatible with this Recommendation, e.g., [ITU-T G.657], may be used for indoor cabling and/or drop section. + +##### A.1.1.2 Transmission direction + +Signals are transmitted both upstream and downstream through the optical transmission medium of the ODN. + +##### A.1.1.3 Transmission method + +Bidirectional transmission is accomplished by use of a wavelength division multiplexing (WDM) technique on a single fibre. + +### A.2 Reference configuration + +The functional reference architecture for a WR-ODN based WDM PON is illustrated in Figure A.1. + + + +The diagram illustrates the functional reference architecture for a WR-ODN based WDM PON. On the left, an 'OLT chassis' contains multiple 'OLT CT' units (CT-1, CT-2, CT-3, ..., CT-n). Each unit is connected to a 'Wavelength router (AN)' via an 'S/R-CP' interface (CP1, CP2, CP3, ..., CPn). The 'OLT chassis' is connected to an 'SNI' (Service Network Interface) on the far left. The 'Wavelength router (AN)' is connected to an 'ODN' (Optical Distribution Network) via an 'S/R-CG' (Service/Routing Connector) reference point. The 'ODN' is a central horizontal line. On the right side of the 'ODN', there is another 'Wavelength router (ODN)' which connects to multiple 'ONU' units (ONU-1, ONU-2, ..., ONU-n). Each 'ONU' is connected to a 'UNI' (User Network Interface) on the far right. The 'Wavelength router (ODN)' is connected to the 'ODN' via an 'R/S' (Restoration/Splitter) reference point. The diagram shows bidirectional arrows on the 'ODN' line, indicating data flow in both directions. + +Functional reference architecture and reference points for WR-ODN based WDM PON diagram + +**Figure A.1 – Functional reference architecture and reference points for WR-ODN based WDM PON** + +The following reference points from Figure A.1 are defined below: + +- S: The sending interface to the network +- R: The receiving interface from the network +- S/R (S/R-CG or S/R-CP), R/S: The S/R-CG and S/R-CP points should be bidirectional mode. Combination of points S and R existing simultaneously in a single fibre, when operating in bidirectional mode. The S/R point is referenced to the OLT side, the R/S point is referenced to the ONU side. + +The two directions for optical transmission in the ODN are defined as follows: + +- Downstream direction for signals travelling from the OLT to the ONU(s); and +- Upstream direction for signals travelling from the ONU(s) to the OLT. + +Transmission in downstream and upstream directions takes place on the same fibre and components (duplex/diplex configuration). + +The primary method of optical parameter specification is in reference to the S/R point for channel group (S/R-CG reference point of Figure A.1 for the individual wavelength channels). This method is used in the PMD tables appearing in clause A.3.7. An alternative informative optical parameter specification method is in reference to the S/R point for channel pair (S/R-CP reference point of Figure A.1). The alternative method is applicable in the situations when the primary reference point, S/R-CG, is not practical or not accessible for performing measurements or it is desirable to provide a simple sensitivity specification to an OLT transceiver vendor. + +Each ONU in Figure A.1 is equipped with a tunable transmitter. The tunable ONU transmitter must be able to adjust to the wavelength channels within the bands specified in Table A.3. + +This Recommendation specifies 12 and 20 wavelength channel pairs (CPs) for wavelength routed PON (WRP) (the frequency plan for 40 wavelength CPs is for further study). The number of wavelength channels supported by a given equipment implementation or network instance is not specified; however, the optical parameter tables should be consulted for the specific assumptions made for the parameters given. + +The architecture can be extended to support multiple OLTs on a common ODN for other purposes such as pay-as-you-grow deployment and spectral flexibility. + +#### **A.2.1 Physical grouping of logical functions** + +The logical functions identified in Figure A.1 for WRP could be considered to be individual physical items, or fully integrated into a single device. + +#### **A.2.2 Optical path loss classes** + +See Table A.4 for recommended classes for optical path loss. + +#### **A.2.3 Categories for fibre differential distance** + +Fibre distance classes are specified in Table A.1. + +**Table A.1 – ODN fibre distance classes** + +| Fibre distance class | Minimum fibre distance (km) | Maximum fibre distance (km) | +|-----------------------------|------------------------------------|------------------------------------| +| DD10 | 0 | 10 | +| DD20 | 0 | 20 | + +### A.3 PMD layer requirements + +All parameters are specified as follows, and are in accordance with Table A.2 to Table A.9. The WDM channel frequency plan is specified in Table A.3, WDM PON line rate options and optical parameter are specified in Table A.2, ODN optical path loss classes (ODN classes) are specified in Table A.4, optical interface parameters of 10G and 25G class are specified in Table A.6 to Table A.9. + +All parameter values specified are worst-case values, to be met over the range of standard operating conditions (i.e., temperature and humidity), 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 the values specified in Table A.6 to Table A.9, for the extreme case of optical path attenuation and dispersion conditions. + +#### A.3.1 Wavelength allocation + +For the downstream direction, the WRP wavelength band is 1529.553-1544.526 nm; for upstream direction, the WDM PON wavelength band is 1550.116-1565.496 nm. These wavelength bands align with those defined in [b-ITU-T G.698.4] to maximize the potential to use common components. + +#### A.3.2 Nominal line rate and clock accuracy + +Parameters to be specified are categorized by downstream and upstream nominal line rates and downstream/upstream rate combinations as shown in Table A.2. Each WDM channel in the channel group on a WDM PON can use any of the line rate options specified in Table A.2. + +**Table A.2 – Relation between WDM PON line rate options and optical parameter tables** + +| Line rate class | Nominal line rate, symmetric downstream/upstream (Gbit/s) | Supported user network interface (UNI) | Optical parameter table, downstream/upstream | +|-----------------|-----------------------------------------------------------|----------------------------------------------------------|----------------------------------------------| +| 10G | 9.8304,
9.95328
10.1376,
10.3125 | CPRI option 7
OC-192
CPRI option 8
10G Ethernet | Table A.6/Table A.8 | +| 25G | 24.33024
25.78125 | CPRI option 10
25G Ethernet | Table A.7/Table A.9 | + +When the OLT and the end office (the facility of the OLT and synchronization source) are in their normal operating state, the OLT is typically traceable to a Stratum-1 reference (accuracy of $1 \times 10^{-11}$ ). When the OLT is in its free running mode, the accuracy of the downstream signal is at least that of a Stratum-4 clock ( $3.2 \times 10^{-5}$ ). OLTs intended for timing-critical applications such as mobile backhaul require Stratum-3 quality in free-running mode. + +NOTE – The OLT may derive its timing from either a dedicated timing signal source or from a synchronous data interface (line timing). A packet-based timing source may also be used. + +#### A.3.3 Line code + +Line coding for WRP is determined by the specific application. + +For 10G/25G Ethernet, the line code is scrambled non-return to zero (NRZ). + +#### A.3.4 Operating wavelength channels + +The operating wavelength bands for WRP are specified in clause A.3.1. + +The WDM channel frequency plan is described in Table A.3. + +**Table A.3 – WDM channel frequency plan** + +| Channel | Downstream Central frequency (THz) | Downstream Central Wavelength (nm) | Upstream Central frequency (THz) | Upstream Central Wavelength (nm) | +|---------|------------------------------------|------------------------------------|----------------------------------|----------------------------------| +| 1 | 194.1 | 1544.526 | 191.5 | 1565.496 | +| 2 | 194.2 | 1543.730 | 191.6 | 1564.679 | +| 3 | 194.3 | 1542.936 | 191.7 | 1563.863 | +| 4 | 194.4 | 1542.142 | 191.8 | 1563.047 | +| 5 | 194.5 | 1541.349 | 191.9 | 1562.233 | +| 6 | 194.6 | 1540.557 | 192.0 | 1561.419 | +| 7 | 194.7 | 1539.766 | 192.1 | 1560.606 | +| 8 | 194.8 | 1538.976 | 192.2 | 1559.794 | +| 9 | 194.9 | 1538.186 | 192.3 | 1558.983 | +| 10 | 195.0 | 1537.397 | 192.4 | 1558.173 | +| 11 | 195.1 | 1536.609 | 192.5 | 1557.363 | +| 12 | 195.2 | 1535.822 | 192.6 | 1556.555 | +| 13 | 195.3 | 1535.036 | 192.7 | 1555.747 | +| 14 | 195.4 | 1534.250 | 192.8 | 1554.940 | +| 15 | 195.5 | 1533.465 | 192.9 | 1554.134 | +| 16 | 195.6 | 1532.681 | 193.0 | 1553.329 | +| 17 | 195.7 | 1531.898 | 193.1 | 1552.524 | +| 18 | 195.8 | 1531.116 | 193.2 | 1551.721 | +| 19 | 195.9 | 1530.334 | 193.3 | 1550.918 | +| 20 | 196.0 | 1529.553 | 193.4 | 1550.116 | +| 21 | FFS | FFS | FFS | FFS | +| 22 | FFS | FFS | FFS | FFS | +| 23 | FFS | FFS | FFS | FFS | +| 24 | FFS | FFS | FFS | FFS | +| 25 | FFS | FFS | FFS | FFS | +| 26 | FFS | FFS | FFS | FFS | +| 27 | FFS | FFS | FFS | FFS | +| 28 | FFS | FFS | FFS | FFS | +| 29 | FFS | FFS | FFS | FFS | +| 30 | FFS | FFS | FFS | FFS | +| 31 | FFS | FFS | FFS | FFS | +| 32 | FFS | FFS | FFS | FFS | +| 33 | FFS | FFS | FFS | FFS | +| 34 | FFS | FFS | FFS | FFS | +| 35 | FFS | FFS | FFS | FFS | +| 36 | FFS | FFS | FFS | FFS | +| 37 | FFS | FFS | FFS | FFS | +| 38 | FFS | FFS | FFS | FFS | +| 39 | FFS | FFS | FFS | FFS | +| 40 | FFS | FFS | FFS | FFS | + +NOTE – Channels 1-12 are assigned to WRP with 12 wavelength CPs. Channels 1-20 are assigned to WRP with 20 wavelength CPs. The frequency plan for 40 wavelength CPs is for further study. + +**Table A.3 – WDM channel frequency plan** + +| Channel | Downstream Central frequency (THz) | Downstream Central Wavelength (nm) | Upstream Central frequency (THz) | Upstream Central Wavelength (nm) | +|---------------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------|----------------------------------|----------------------------------| +| The frequency values in this table are normative, while the wavelength values are for information only. | | | | | + +#### A.3.5 FEC code selection + +The choice of FEC depends on the service protocol. + +For common public radio interface (CPRI) with 64B/66B coding, FEC is optional. + +For 10G Ethernet and 25G Ethernet, the FEC code is RS (528, 514) (clause 108 of [b-IEEE 802.3-2022]). + +#### A.3.6 Electronic dispersion compensation + +Electronic dispersion compensation (EDC) may be used in the OLT (ONU) transmitter to achieve the optical path penalty (OPP) specified in the optical interface parameter tables. At the ONU (OLT) receiver, EDC may also be used. + +#### A.3.7 PMD parameters + +##### A.3.7.1 Compatible ODN + +ODN optical path loss classes (ODN classes) are specified in Table A.4. + +The optical path loss for each class is specified between the S/R-CG and R/S reference points in either direction. + +**Table A.4 – ODN optical path loss classes (ODN classes) for wavelength router (WR)-based WDM PON reference logical architecture** + +| | Class X (10 km) | Class Y (20 km) | +|----------------------------------------|-----------------|-----------------| +| Minimum optical path loss | 3.2 dB | 3.2 dB | +| Maximum optical path loss | 13 dB | 17 dB | +| Maximum differential optical path loss | 8 dB | 12 dB | + +WRP shall operate over an ODN whose parameters are described in Table A.5. + +**Table A.5 – Physical parameters of a simple ODN (ODS)** + +| Item | Unit | Specification | +|---------------------------------------------------|------|------------------------------------| +| Fibre type | – | [ITU-T G.652] or compatible | +| Attenuation range | dB | Class X: 3.2-13
Class Y: 3.2-17 | +| Maximum fibre distance between S/R and R/S points | km | DD10: 10
DD20: 20 | +| Minimum fibre distance between S/R and R/S points | km | 0 | +| Bidirectional transmission | – | 1-fibre WDM | +| Maintenance wavelength | nm | FFS | + +##### A.3.7.2 Optical interface parameters + +###### A.3.7.2.1 Optical interface parameters of downstream direction + +The following downstream optical interface tables are applicable for up to 20 km fibre length. + +**Table A.6 – Optical interface parameters for 10G class (from 9.8304 Gbit/s to 10.3125 Gbit/s) downstream direction** + +| Item | Unit | Value | | +|---------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| OLT transmitter (optical interface S) | | | | +| Nominal line rate | Gbit/s | 9.8304 to 10.3125 | | +| Operating wavelength band | nm | 1529.553-1544.526 | | +| Operating central frequency | THz | Table A.3 | | +| Operating channel spacing | GHz | 100 | | +| Maximum spectral excursion | GHz | $\pm 20$ | | +| Line code | – | Determined by application
(Scrambled NRZ assumed for parameter values) | | +| Mask of the transmitter eye diagram | – | See clause A.3.8.6 | | +| Maximum reflectance of equipment at S/R-CG, measured at transmitter wavelength | dB | Not applicable | | +| Minimum ORL of ODN at S/R-CG | dB | 32 | | +| ODN class | | X | Y | +| Mean channel launch power minimum (at S/R-CG) without FEC | dBm | –8 | –4 | +| Mean channel launch power minimum (at S/R-CG) with FEC | dBm | FFS | FFS | +| Mean channel launch power maximum (at S/R-CG) without FEC | dBm | –4 | 0 | +| Mean channel launch power maximum (at S/R-CG) with FEC | dBm | FFS | FFS | +| Maximum downstream WNE-PSD | dBm | FFS | | +| Minimum extinction ratio (Note 1) | dB | 6 | | +| Tolerance to reflected optical power | dB | –15 | | +| Dispersion range (Note 2) | ps/nm | $0 \text{ to } \frac{0.092 \times \lambda}{4} \left[ 1 - \left( \frac{1300}{\lambda} \right)^2 \right] \times 10 \text{ (DD10),}$
$0 \text{ to } \frac{0.092 \times \lambda}{4} \left[ 1 - \left( \frac{1300}{\lambda} \right)^2 \right] \times 20 \text{ (DD20)}$ | | +| Minimum side mode suppression ratio (at S/R-CP) (Note 3) | dB | 30 | | +| Maximum downstream per channel out-of-band optical power spectral density (PSD) | dBm | FFS | | +| Maximum downstream per channel out-of-channel optical PSD | dBm | FFS | | +| Jitter generation | – | See clause A.3.8.6.3 | | +| ONU receiver (optical interface R) | | | | + +**Table A.6 – Optical interface parameters for 10G class (from 9.8304 Gbit/s to 10.3125 Gbit/s) downstream direction** + +| Item | Unit | Value | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------------|------|--|--| +| Maximum OPP (Note 4) | dB | 2.5 | | | | +| Maximum reflectance of equipment at R/S, measured at receiver wavelength | dB | FFS | | | | +| ODN class | | X | Y | | | +| Sensitivity (at R/S) @ BER= $10^{-12}$ | dBm | -23.5 | | | | +| Sensitivity (at R/S) @ BER= $10^{-3}$ (Note 5) | dBm | FFS | FFS | | | +| Overload (at R/S) @ BER= $10^{-12}$ | dBm | -7.2 | -3.2 | | | +| Overload (at R/S) @ BER= $10^{-3}$ (Note 5) | dBm | FFS | FFS | | | +| In-band crosstalk tolerance | dB | FFS | | | | +| Consecutive identical digit immunity | bit | 72 | | | | +| Jitter tolerance | – | See clause A.3.8.6.3 | | | | +| NOTE 1 – A lower extinction ratio is allowed but must be compensated by a larger transmitter launch power within the limits of the "Mean launch power maximum" value. However, the impact of reduced ER on OOB/OOC power must be considered. | | | | | | +| NOTE 2 – This formula (see clause 6.10 of [ITU-T G.652]) is used instead of the worst-case value due to the large variation of dispersion within the WRP wavelength band. This allows implementers to build devices only to the desired dispersion specification. $\lambda$ is the longest possible wavelength in each channel, in nanometre units, considering the spectral excursion. | | | | | | +| NOTE 3 – For downstream, side mode suppression ratio (SMSR) is measured on the laser output, before any filtering. This prevents a significant mode partition noise penalty. | | | | | | +| NOTE 4 – The specified OPP is valid up to a 20-channel system. If the actual OPP is worse than the specified value, it must be compensated by the transmitter launch power increase up to the limits of the Mean launch power maximum. | | | | | | +| NOTE 5 – See clause 9.4.1 of [b-ITU-T G.Sup39] for additional details. | | | | | | + +**Table A.7 – Optical interface parameters for 25G class (from 24.33024 Gbit/s to 25.78125 Gbit/s) downstream direction** + +| Item | Unit | Value | +|----------------------------------------------|--------|---------------------------------------------------------------------------| +| OLT transmitter (optical interface S) | | | +| Nominal line rate | Gbit/s | 24.33024-25.78125 | +| Operating wavelength band | nm | 1529.553-1544.526 | +| Operating central frequency | THz | Table A.3 | +| Operating channel spacing | GHz | 100 | +| Maximum spectral excursion | GHz | $\pm 20$ | +| Line code | – | Determined by application
(Scrambled NRZ assumed for parameter values) | +| Mask of the transmitter eye diagram | – | See clause A.3.8.6 | + +**Table A.7 – Optical interface parameters for 25G class (from 24.33024 Gbit/s to 25.78125 Gbit/s) downstream direction** + +| Item | Unit | Value | +|--------------------------------------------------------------------------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Maximum reflectance of equipment at S/R-CG, measured at transmitter wavelength | dB | Not applicable | +| Minimum ORL of ODN at S/R-CG | dB | 32 | +| ODN class | | X | +| Mean channel launch power minimum (at S/R-CG) without FEC | dBm | FFS | +| Mean channel launch power minimum (at S/R-CG) with FEC | dBm | -4 | +| Mean channel launch power maximum (at S/R-CG) without FEC | dBm | FFS | +| Mean channel launch power maximum (at S/R-CG) with FEC | dBm | 0 | +| Maximum downstream WNE-PSD | dBm | FFS | +| Minimum extinction ratio (Note 1) | dB | 8 | +| Tolerance to reflected optical power | dB | -15 | +| Dispersion range (Note 2) | ps/nm | 0 to $\frac{0.092 \times \lambda}{4} \left[ 1 - \left( \frac{1300}{\lambda} \right)^2 \right] \times 10$ (DD10),
0 to $\frac{0.092 \times \lambda}{4} \left[ 1 - \left( \frac{1300}{\lambda} \right)^2 \right] \times 20$ (DD20) | +| Minimum side mode suppression ratio (at S/R-CP) (Note 3) | dB | 30 | +| Maximum downstream per channel out-of-band optical PSD | dBm | FFS | +| Maximum downstream per channel out-of-channel optical PSD | dBm | FFS | +| Jitter generation | – | See clause A.3.8.6.3 | +| ONU receiver (optical interface R) | | | +| Maximum OPP (Note 4) | dB | 3 | +| Maximum reflectance of equipment at R/S, measured at receiver wavelength | dB | FFS | +| ODN class | | X | +| Sensitivity (at R/S) @ BER= $10^{-12}$ | dBm | FFS | +| Sensitivity (at R/S) @ BER= $5 \times 10^{-5}$ (Note 5) | dBm | -20 | +| Overload (at R/S) @ BER= $10^{-12}$ | dBm | FFS | +| Overload (at R/S) @ BER= $5 \times 10^{-5}$ (Note 5) | dBm | -3.2 | +| In-band crosstalk tolerance | dB | FFS | +| Consecutive identical digit immunity | bit | 72 | +| Jitter tolerance | – | See clause A.3.8.6.3 | + +**Table A.7 – Optical interface parameters for 25G class (from 24.33024 Gbit/s to 25.78125 Gbit/s) downstream direction** + +| Item | Unit | Value | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------| +| NOTE 1 – A lower extinction ratio is allowed but must be compensated by a larger transmitter launch power within the limits of the "Mean launch power maximum" value. However, the impact of reduced ER on OOB/OOC power must be considered.
NOTE 2 – This formula (see clause 6.10 of [ITU-T G.652]) is used instead of the worst-case value due to the large variation of dispersion within the WRP wavelength band. This allows implementers to build devices only to the desired dispersion specification. $\lambda$ is the longest possible wavelength in each channel, in nanometre units, considering the spectral excursion.
NOTE 3 – For downstream, SMSR is measured on the laser output, before any filtering. This prevents a significant mode partition noise penalty.
NOTE 4 – The specified OPP is valid up to a 20-channel system. If the actual OPP is worse than the specified value, it must be compensated by the transmitter launch power increase up to the limits of the Mean launch power maximum.
NOTE 5 – See clause 9.4.1 of [b-ITU-T G.Sup39] for additional details. | | | + +###### A.3.7.2.2 Optical interface parameters of upstream direction + +The following upstream optical interface tables are applicable for up to 20 km fibre length. + +**Table A.8 – Optical interface parameters for 10G class (from 9.8304 Gbit/s to 10.3125 Gbit/s) upstream direction** + +| Item | Unit | Value | | +|-----------------------------------------------------------------------------|--------|---------------------------------------------------------------------------|-----| +| ONU transmitter (optical interface S) | | | | +| Nominal line rate | Gbit/s | 9.8304 to 10.3125 | | +| Operating wavelength band | nm | 1550.116-1565.496 | | +| Operating channel spacing | GHz | 100 | | +| Line code | – | Determined by application
(Scrambled NRZ assumed for parameter values) | | +| Mask of the transmitter eye diagram | – | See clause A.3.8.6 | | +| Maximum reflectance of equipment at R/S, measured at transmitter wavelength | dB | FFS | | +| Minimum ORL of ODN at R/S | dB | 32 | | +| ODN Class | | X | Y | +| Mean channel launch power minimum (at R/S) without FEC | dBm | –1 | –1 | +| Mean channel launch power minimum (at R/S) with FEC | dBm | FFS | FFS | +| Mean channel launch power maximum (at R/S) without FEC | dBm | 4 | 4 | +| Mean channel launch power minimum (at R/S) with FEC | dBm | FFS | FFS | +| Minimum extinction ratio (Note 1) | dB | 6 | | +| Tolerance to reflected optical power | dB | –15 | | + +**Table A.8 – Optical interface parameters for 10G class (from 9.8304 Gbit/s to 10.3125 Gbit/s) upstream direction** + +| Item | Unit | Value | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--|--| +| Dispersion range (Note 2) | ps/nm | $0 \text{ to } \frac{0.092 \times \lambda}{4} \left[ 1 - \left( \frac{1300}{\lambda} \right)^2 \right] \times 10 \quad (\text{DD10}),$
$0 \text{ to } \frac{0.092 \times \lambda}{4} \left[ 1 - \left( \frac{1300}{\lambda} \right)^2 \right] \times 20 \quad (\text{DD20})$ | | | | +| Minimum side mode suppression ratio (Note 3) | dB | 30 | | | | +| Maximum upstream out-of-band optical PSD | dBm | FFS | | | | +| Maximum upstream out-of-channel optical PSD – OOC1 | dBm | FFS | | | | +| Maximum upstream out-of-channel optical PSD – OOC2 | dBm | FFS | | | | +| Jitter transfer | – | See clause A.3.8.6.3 | | | | +| Jitter generation | – | See clause A.3.8.6.3 | | | | +| OLT receiver (optical interface R) | | | | | | +| Maximum OPP (Note 4) | dB | 2.5 | | | | +| Maximum reflectance of equipment at S/R-CG, measured at receiver wavelength | dB | FFS | | | | +| ODN Class | | X | Y | | | +| Sensitivity (at S/R-CG) @ BER= $10^{-12}$ | dBm | –20.5 | –28.5 | | | +| Sensitivity (at S/R-CG) @ BER= $10^{-3}$ (Note 5) | dBm | FFS | FFS | | | +| Overload (at S/R-CG) @ BER= $10^{-12}$ | dBm | 3 | –5 | | | +| Overload (at S/R-CG) @ BER= $10^{-3}$ (Note 5) | dBm | FFS | FFS | | | +| In-band crosstalk tolerance | dB | FFS | | | | +| Consecutive identical digit immunity | bit | 72 | | | | +| Jitter tolerance | – | See clause A.3.8.6.3 | | | | +| NOTE 1 – A lower extinction ratio must be compensated by a larger transmitter launch power within the limits of the mean launch power maximum value. | | | | | | +| NOTE 2 – This formula (see clause 6.10 of [ITU-T G.652]) is used instead of the worst-case value due to the large variation of dispersion within the WRP wavelength band. This allows implementers to build devices only to the desired dispersion specification. $\lambda$ is the longest possible wavelength in each channel, in nanometre units, considering the spectral excursion. | | | | | | +| NOTE 3 – For upstream at the ONU, SMSR is measured on the laser output, before any filtering. This prevents a significant mode partition noise penalty. | | | | | | +| NOTE 4 – The specified OPP is valid up to a 20-channel system. If the actual OPP is worse than the specified value, it must be compensated by the transmitter launch power increase up to the limits of the Mean launch power maximum. | | | | | | +| NOTE 5 – See clause 9.4.1 of [b-ITU-T G.Sup39] for additional details. | | | | | | + +**Table A.9 – Optical interface parameters for 25G class (from 24.33024 Gbit/s to 25.78125 Gbit/s) upstream direction** + +| Item | Unit | Value | +|-----------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ONU transmitter (optical interface S) | | | +| Nominal line rate | Gbit/s | 24.33024-25.78125 | +| Operating wavelength band | nm | 1550.116-1565.496 | +| Operating channel spacing | GHz | 100 | +| Line code | – | Determined by application
(Scrambled NRZ assumed for parameter values) | +| Mask of the transmitter eye diagram | – | See clause A.3.8.6 | +| Maximum reflectance of equipment at R/S, measured at transmitter wavelength | dB | FFS | +| Minimum ORL of ODN at R/S | dB | 32 | +| ODN Class | | X | +| Mean channel launch power minimum (at R/S) without FEC | dBm | FFS | +| Mean channel launch power minimum (at R/S) with FEC | dBm | –1 | +| Mean channel launch power maximum (at R/S) without FEC | dBm | FFS | +| Mean channel launch power minimum (at R/S) with FEC | dBm | 3 | +| Minimum extinction ratio (Note 1) | dB | 8 | +| Tolerance to reflected optical power | dB | –15 | +| Dispersion range (Note 2) | ps/nm | 0 to $\frac{0.092 \times \lambda}{4} \left[ 1 - \left( \frac{1300}{\lambda} \right)^2 \right] \times 10$ (DD10),
0 to $\frac{0.092 \times \lambda}{4} \left[ 1 - \left( \frac{1300}{\lambda} \right)^2 \right] \times 20$ (DD20) | +| Minimum side mode suppression ratio (Note 3) | dB | 30 | +| Maximum upstream out-of-band optical PSD | dBm | FFS | +| Maximum upstream out-of-channel optical PSD – OOC1 | dBm | FFS | +| Maximum upstream out-of-channel optical PSD – OOC2 | dBm | FFS | +| Jitter transfer | – | See clause A.3.8.6.3 | +| Jitter generation | – | See clause A.3.8.6.3 | +| OLT receiver (optical interface R) | | | +| Maximum OPP (Note 4) | dB | 3 | +| Maximum reflectance of equipment at S/R-CG, measured at receiver wavelength | dB | FFS | +| ODN Class | | X | + +**Table A.9 – Optical interface parameters for 25G class (from 24.33024 Gbit/s to 25.78125 Gbit/s) upstream direction** + +| Item | Unit | Value | +|---------------------------------------------------------------|------|----------------------| +| Sensitivity (at S/R-CG) @ BER= $10^{-12}$ | dBm | FFS | +| Sensitivity (at S/R-CG) @ BER= $5 \times 10^{-5}$
(Note 5) | dBm | -17 | +| Overload (at S/R-CG) @ BER= $10^{-12}$ | dBm | FFS | +| Overload (at S/R-CG) @ BER= $5 \times 10^{-5}$
(Note 5) | dBm | -0.2 | +| In-band crosstalk tolerance | dB | FFS | +| Consecutive identical digit immunity | bit | 72 | +| Jitter tolerance | – | See clause A.3.8.6.3 | + +NOTE 1 – A lower extinction ratio must be compensated by a larger transmitter launch power within the limits of the mean launch power maximum value. +NOTE 2 – This formula (see clause 6.10 of [ITU-T G.652]) is used instead of the worst-case value due to the large variation of dispersion within the WRP wavelength band. This allows implementers to build devices only to the desired dispersion specification. $\lambda$ is the longest possible wavelength in each channel, in nanometre units, considering the spectral excursion. +NOTE 3 – For upstream at the ONU, SMSR is measured on the laser output, before any filtering. This prevents a significant mode partition noise penalty. +NOTE 4 – The specified OPP is valid up to a 20-channel system. If the actual OPP is worse than the specified value, it must be compensated by the transmitter launch power increase up to the limits of the Mean launch power maximum. +NOTE 5 – See clause 9.4.1 of [b-ITU-T G.Sup39] for additional details. + +#### A.3.8 Transmitter at reference point S + +All parameters are defined as follows and are in accordance with Table A.6 to Table A.9. + +##### A.3.8.1 Source type + +Considering the attenuation/dispersion characteristics of the target fibre channel, feasible transmitter devices include only single-longitudinal mode (SLM) lasers. The indication of a nominal source type in this Recommendation is not a requirement though it is also expected that only SLM lasers meet all the distance and line rate requirements of the WRP system both for the downstream and upstream links. + +##### A.3.8.2 Spectral characteristics + +For SLM lasers, the laser is specified by its fibre dispersion range, the range over which the laser characteristics and fibre dispersion result in a defined penalty at a specified fibre distance, under standard operating conditions. Additionally, for control of mode partition noise in SLM systems, a minimum value for the laser side-mode suppression ratio is specified. The actual spectral characteristics are limited by the maximum amount of OPP produced with the worst-case optical dispersion in the data signal. + +##### A.3.8.3 Operating wavelength band + +Operating wavelength band specification options are summarized in Table A.3. + +##### A.3.8.4 Nominal central frequency + +The central frequencies are based on the frequency grid given in [ITU-T G.694.1]. The downstream central frequencies are specified in Table A.3. + +Note that the value of "c" (speed of light in a vacuum) that is used for converting between frequency and wavelength is $2.99792458 \times 10^8$ m/s. + +##### A.3.8.5 Mean launch optical power + +The mean launch optical power is specified as a range to allow for some cost optimization and to cover all allowances for operation under standard operating conditions, transmitter connector degradation, measurement tolerances and ageing effects. + +In the operating state, the lower figure is the minimum power to be provided and the higher one is the power never to be exceeded. + +##### A.3.8.6 Mask of transmitter eye diagram + +This clause specifies the pulse shape characteristics for the OLT and ONU transmitters. For the purpose of assessing the transmit signal, it is important to consider not only the eye opening, but also the overshoot and undershoot limitations. + +###### A.3.8.6.1 OLT transmitter + +The parameters specifying the mask of the eye diagram (see Figure A.2) for the OLT transmitter are shown in Table A.10. The test set-up for the measurement of the mask of the eye diagram is shown in Figure A.3. + + + +G.9802.2(23) + +Figure A.2: Mask of the eye diagram for OLT. The diagram shows a normalized eye diagram with a central eye opening. The vertical axis represents normalized amplitude from -y3 to 1+y3, with key levels at 0 (mean level of logical '0'), 1 (mean level of logical '1'), and various thresholds (y1, y2, 1-y1, 1-y2). The horizontal axis represents normalized time from 0 to 1, with key points at x1, x2, x3, 1-x3, 1-x2, and 1-x1. The eye opening is shaded in dark grey, and the surrounding mask area is light grey. The text 'G.9802.2(23)' is visible at the bottom right of the diagram. + +Figure A.2 – Mask of the eye diagram for OLT + +**Table A.10 – Mask of the eye diagram for OLT transmitter – Numeric values** + +| | 10G | 25G | +|-------------------|--------------------|--------------------| +| x1 | 0.25 | 0.25 | +| x2 | 0.4 | 0.4 | +| x3 | 0.45 | 0.45 | +| y1 | 0.25 | 0.25 | +| y2 | 0.28 | 0.28 | +| y3 | 0.4 | 0.4 | +| Maximum hit ratio | $5 \times 10^{-5}$ | $5 \times 10^{-5}$ | + +NOTE – The values are taken from clause 7.2.2.14 of [b-ITU-T G.959.1], "NRZ 10G Ratio small" and "NRZ 25G Ratio". The "hit ratio" is the acceptable ratio of samples inside to outside the shaded area. + + + +``` + +graph LR + A[Optical transmitter] --> B[Attenuatora)] + B --> C["O/E converter +fourth-order +Thomson filterb)"] + C --> D[Waveform monitor] + +``` + +G.9802.2(23) + +Block diagram of the test set-up for measuring the mask of the eye diagram for OLT transmitter. The components are: Optical transmitter, Attenuator (optional), O/E converter fourth-order Thomson filter, and Waveform monitor. The diagram is labeled G.9802.2(23). + +a) Attenuator is used if necessary. + +b) Cut-off frequency (3 dB attenuation frequency) of the filter is 0.75 times output nominal bit rate. + +**Figure A.3 – Test set-up for measuring the mask of the eye diagram for OLT transmitter** + +###### **A.3.8.6.2 ONU transmitter** + +###### **A.3.8.6.2.1 ONU transmitter eye diagram** + +The parameters specifying the mask of the eye diagram (see Figure A.4) for the ONU transmitter are shown in Table A.11. The test set-up for the measurement of the mask of the eye diagram is shown in Figure A.5. + + + +The figure shows an eye diagram with a shaded mask. The horizontal axis represents normalized time from 0 to 1. The vertical axis represents normalized voltage from $-y_3$ to $1+y_3$ . Key parameters marked on the horizontal axis are $x_1, x_2, x_3, 1-x_3, 1-x_2$ , and $1-x_1$ . Key parameters marked on the vertical axis are $y_1, y_2, y_3, 1-y_1$ , and $1-y_2$ . Two horizontal dashed lines indicate the mean level of the center of logical "1" and logical "0". The shaded area represents the acceptable region for the eye diagram. The diagram is labeled G.9802.2(23). + +Eye diagram mask for ONU transmitter showing various parameters like x1, x2, x3, y1, y2, y3, and mean levels for logical 1 and 0. The diagram is labeled G.9802.2(23). + +**Figure A.4 – Mask of the eye diagram for ONU transmitter** + +**Table A.11 – Mask of the eye diagram for ONU transmitter – numeric values** + +| | | | +|----------------------------------------------------------------------------------------------|----------------------|----------------------| +| | 10G | 25G | +| x1 | 0.25 | 0.25 | +| x2 | 0.4 | 0.4 | +| x3 | 0.45 | 0.45 | +| y1 | 0.25 | 0.25 | +| y2 | 0.28 | 0.28 | +| y3 | 0.4 | 0.4 | +| Maximum hit ratio | 5 × 10 −5 | 5 × 10 −5 | +| NOTE – The "hit ratio" is the acceptable ratio of samples inside to outside the shaded area. | | | + + + +[Test set-up] + +``` + +graph LR + A[Optical transmitter] --> B[Attenuatora)] + B --> C["O/E converter +fourth-order +Thomson filterb)"] + C --> D[Waveform monitor] + +``` + +a) Attenuator is used if necessary. +b) Cut-off frequency (3 dB attenuation frequency) of the filter is 0.75 times output nominal bit rate. + +**Figure A.5 – Test set-up for measuring the mask of the eye diagram for ONU transmitter** + +Block diagram of the test set-up for measuring the mask of the eye diagram for ONU transmitter. It consists of four blocks connected in series: Optical transmitter, Attenuator (with footnote a), O/E converter fourth-order Thomson filter (with footnote b), and Waveform monitor. Arrows indicate the signal flow from left to right. + +**A.3.8.6.3 Jitter performance** + +This clause describes jitter requirements for optical interfaces of WDM PON. + +**A.3.8.6.3.1 Jitter transfer** + +The jitter transfer specification applies only to the ONU. + +The jitter transfer function is defined as: + +$$\text{jitter transfer} = 20\log_{10} \left[ \frac{\text{jitter on upstream signal UI}}{\text{jitter on downstream signal UI}} \times \frac{\text{downstream bit rate}}{\text{upstream bit rate}} \right]$$ + +The jitter transfer function of an ONU shall be under the curve given in Figure A.6, when input sinusoidal jitter up to the mask level in Figure A.7 is applied, with the parameters specified in this figure for each line rate. + +**Rec. ITU-T G.9802.2 (07/2023)** 21 + + + +| Line rate class | $f_L$ (kHz) | $f_C$ (kHz) | $f_H$ (kHz) | P (dB) | +|-----------------|-------------|-------------|-------------|--------| +| 10 G | 10 | 4000 | 80 000 | 0.1 | +| 25 G | 10 | 4000 | 200 000 | 0.1 | + +G.9802.2(23) + +Figure A.6: Jitter transfer for ONU. A graph showing Jitter gain (P) vs Frequency (fL, fC, fH). The gain is constant at P from fL to fC, then decreases with a slope of -20 dB/dec until fH. Below the graph is a table with line rate class, fL, fC, fH, and P. + +**Figure A.6 – Jitter transfer for ONU** + + + +| Line rate class | $A_3$ (UI) | $A_4$ (UI) | $f_2$ (kHz) | $f_3$ (kHz) | +|-----------------|------------|------------|-------------|-------------| +| 10 G | 1.5 | 0.15 | 400 | 4000 | +| 25 G | 1.5 | 0.15 | 400 | 4000 | + +G.9802.2(23) + +Figure A.7: High-band portion of sinusoidal jitter mask for jitter transfer. A graph showing Input jitter amplitude (A3, A4) vs Frequency (f2, f3). The amplitude is constant at A3 from 0 to f2, then decreases with a slope of -20 dB/dec until f3, where it becomes constant at A4. Below the graph is a table with line rate class, A3, A4, f2, and f3. + +**Figure A.7 – High-band portion of sinusoidal jitter mask for jitter transfer** + +###### **A.3.8.6.3.2 Jitter tolerance** + +Jitter tolerance is defined as the peak-to-peak amplitude of sinusoidal jitter applied on the input of WDM PON signal that causes a 1 dB optical power penalty at the optical receiver. Note that it is a stress test to ensure that no additional penalty is incurred under typical operating conditions. + +The ONU must tolerate, as a minimum, the input jitter applied according to the mask in Figure A.8, with the parameters specified in that figure for the downstream line rate. The OLT must tolerate, as a minimum, the input jitter applied according to the mask in Figure A.8, with the parameters specified in that figure for the upstream line rate. The jitter tolerance specification for the OLT is informative as it can only be measured in a setting that permits continuous operation of the upstream. + + + +| Line rate class | $f_0$ [kHz] | $f_t$ [kHz] | $A_1$ [UIp-p] | $A_2$ [UIp-p] | +|-----------------|-------------|-------------|---------------|---------------| +| 10 G | 400 | 4000 | 0.075 | 0.75 | +| 25 G | 400 | 4000 | 0.075 | 0.75 | + +G.9802.2(23) + +Figure A.8: Jitter tolerance mask graph and table. The graph shows Input jitter amplitude (A1, A2) vs Frequency (f0, ft) with a slope of -20 dB/dec. The table provides values for Line rate class, f0, ft, A1, and A2. + +**Figure A.8 – Jitter tolerance mask** + +###### A.3.8.6.3.3 Jitter generation + +An ONU must not generate a peak-to-peak jitter amplitude more than shown in Table A.12 at line rates of 10G and 25G classes, with no jitter applied to the downstream input and with a measurement bandwidth as specified in Table A.12. An OLT must not generate a peak-to-peak jitter amplitude more than shown in Table A.12 with no jitter applied to its timing reference input and with a measurement band as specified in Table A.12. + +**Table A.12 – Jitter generation requirements** + +| Line rate class | Measurement band
(-3 dB frequencies)
(Note 1) | | Peak-peak amplitude
(UI)
(Note 2) | +|-----------------|-----------------------------------------------------|------------------------------|-----------------------------------------| +| | high-pass
(kHz) | low-pass (MHz)
-60 dB/dec | | +| 10G | 20 | 80 | 0.30 | +| | 4 000 | 80 | 0.10 | +| 25G | 50 | 200 | 0.30 | +| | 4 000 | 200 | 0.10 | + +NOTE 1 – The high-pass and low-pass measurement filter transfer functions are defined in clause 5 of [ITU-T G.825]. + +NOTE 2 – The measurement time and pass/fail criteria are defined in clause 5 of [ITU-T G.825]. + +## Annex B + +## Transmission convergence layer specification + +(This annex forms an integral part of this Recommendation.) + +### B.1 WDM PON management TC layer overview + +TC layer provides a similar operational experience as for legacy PON systems such as G-PON (ITU-T G.984.x Series Recommendations). Thus, features such as silent start, power saving, and capability to map a local PLOAM channel are captured. + +The TC layer supports a WDM PON system containing a set of WDM channels. + +This section overviews the management TC layer. Any reference to one channel termination clearly pertains to a set of one downstream wavelength channel and one upstream wavelength channel. The term optical line termination channel termination (OLT CT) is generically used to address the channel termination. + +The remainder of clause B.1 is structured as follows. Clause B.1.1 introduces the distinct channel modes of WDM PON channels; clause B.1.2 describes WDM PON system supported line rates; clause B.1.3 discusses the principles and identifiers. + +#### B.1.1 WDM PON management channel modes + +In WDM PON, the user data path and the operation, administration and maintenance (OAM) data path are separate through the TC layer. The user data is unprocessed by the TC layer, while the OAM data is processed by the WDM PON management TC layer. + +There are two distinct modes of WDM PON management channels: transparent and transcoded. At the highest level, the arrangement of functions of these two modes is shown in Figure B.1. In transparent mode, both the user data and the WDM PON management TC data are passed directly to the PMD. In this case, the PMD has two separate interfaces. Transparent mode is basically agnostic to the bitrate and protocol of client signal. Transcoded mode is to transform the user data to add OAM features. In transcoded mode, the user data and framed WDM PON management TC data are passed to the two interfaces of the transcoder. The transcoder multiplexes and processes the two streams, and passes the result to the PMD. + + + +``` +graph TD; subgraph Transparent_mode [Transparent mode]; OAM_clients1[OAM clients] --- WDM_PON_management_TC1[WDM PON management TC]; WDM_PON_management_TC1 --- WDM_PON_port1[WDM PON port]; User_data1[User data] --- Data_port1[Data port]; WDM_PON_port1 --- PMD1[PMD]; Data_port1 --- PMD1; end; subgraph Transcoded_mode [Transcoded mode]; OAM_clients2[OAM clients] --- WDM_PON_management_TC2[WDM PON management TC]; WDM_PON_management_TC2 --- WDM_PON_port2[WDM PON port]; User_data2[User data] --- Data_port2[Data port]; WDM_PON_port2 --- Transcoder[Transcoder]; Data_port2 --- Transcoder; Transcoder --- Data_port3[Data port]; Data_port3 --- PMD2[PMD]; end; +``` + +Figure B.1: Relationship of the WDM PON management TC layer with other system functions. The diagram shows two modes: Transparent mode and Transcoded mode. In Transparent mode, OAM clients connect to a WDM PON management TC block, which connects to a WDM PON port of a PMD. User data connects directly to a Data port of the same PMD. In Transcoded mode, OAM clients connect to a WDM PON management TC block, which connects to a WDM PON port of a Transcoder. User data connects to a Data port of the Transcoder. The Transcoder connects to a Data port of a PMD. + +G.9802.2(23) + +**Figure B.1 – Relationship of the WDM PON management TC layer with other system functions** + +#### **B.1.2 Supported nominal line rates** + +The management TC layer specification is applicable to the OLT CTs that support the nominal line rate combination options defined in Annex A. + +The management TC layer specification is applicable to ONUs that support a nominal line rate combination defined in Annex A. + +#### **B.1.3 WDM architecture** + +##### **B.1.3.1 Overview** + +For a WDM PON system, the WDM aspect is represented by multiple OLT CTs, each OLT CT providing bi-directional connectivity through a pair of wavelengths constituting a channel pair (CP), OLT CTs are independent from one another, in line rates and modulation format. + +##### **B.1.3.2 Identifiers common for WRP** + +###### **B.1.3.2.1 WRP system identifier** + +A WRP system identifier (SYS ID) is a 20-bit number that identifies a specific WRP system among multiple systems under common administration. The SYS ID may be coded to include data to support administration such as an operator name, geographical location, service profile, and whether the system is for protection. It is supplied by an EMS/OSS to the OLT CT and is identical for all WDM channels within the system. An ONU stores the SYS ID and uses it as a reference. + +###### **B.1.3.2.2 WRP CT identifier** + +A WRPCT-ID is a 34-bit structured number that uniquely identifies a WRP channel termination (CT) entity within a domain. + +In a WRP system, WRPCT-ID consists of a 28-bit administrative label and a 6-bit WLCH ID. The administrative label is supplied by an EMS/OSS to the OLT NE. It is expected to follow some consistent physical or logical equipment numbering plan, and is treated transparently by the OLT. + +The WRPCT-ID of the specific WRP channel termination is carried within the operation control (OC) structure of the physical synchronization block (PSB) field. + +###### **B.1.3.2.3 Downstream wavelength channel identifier** + +In a WRP system, downstream wavelength channel ID (DWLCH ID) is a 6-bit number that identifies a downstream wavelength channel and is equal to the ordinal number of the channel defined in Table A.3, converted to the range from 0 to 39, as shown in Table B.1. + +**Table B.1 – DWLCH ID to channel mapping** + +| Channel | Frequency (THz) | Wavelength (nm) | DWLCH ID | +|----------------|------------------------|------------------------|-----------------| +| 1 | 194.1 | 1 544.526 | 000000 | +| 2 | 194.2 | 1 543.730 | 000001 | +| 3 | 194.3 | 1 542.936 | 000010 | +| 4 | 194.4 | 1 542.142 | 000011 | +| 5 | 194.5 | 1 541.349 | 000100 | +| 6 | 194.6 | 1 540.557 | 000101 | +| 7 | 194.7 | 1 539.766 | 000110 | +| 8 | 194.8 | 1 538.976 | 000111 | +| 9 | 194.9 | 1 538.186 | 001000 | +| 10 | 195.0 | 1 537.397 | 001001 | + +**Table B.1 – DWLCH ID to channel mapping** + +| Channel | Frequency (THz) | Wavelength (nm) | DWLCH ID | +|---------|-----------------|-----------------|----------| +| 11 | 195.1 | 1 536.609 | 001010 | +| 12 | 195.2 | 1 535.822 | 001011 | +| 13 | 195.3 | 1 535.036 | 001100 | +| 14 | 195.4 | 1 534.250 | 001101 | +| 15 | 195.5 | 1 533.465 | 001110 | +| 16 | 195.6 | 1 532.681 | 001111 | +| 17 | 195.7 | 1 531.898 | 010000 | +| 18 | 195.8 | 1 531.116 | 010001 | +| 19 | 195.9 | 1 530.334 | 010010 | +| 20 | 196.0 | 1 529.553 | 010011 | +| 21 | FFS | FFS | 010100 | +| 22 | FFS | FFS | 010101 | +| 23 | FFS | FFS | 010110 | +| 24 | FFS | FFS | 010111 | +| 25 | FFS | FFS | 011000 | +| 26 | FFS | FFS | 011001 | +| 27 | FFS | FFS | 011010 | +| 28 | FFS | FFS | 011011 | +| 29 | FFS | FFS | 011100 | +| 30 | FFS | FFS | 011101 | +| 31 | FFS | FFS | 011110 | +| 32 | FFS | FFS | 011111 | +| 33 | FFS | FFS | 100000 | +| 34 | FFS | FFS | 100001 | +| 35 | FFS | FFS | 100010 | +| 36 | FFS | FFS | 100011 | +| 37 | FFS | FFS | 100100 | +| 38 | FFS | FFS | 100101 | +| 39 | FFS | FFS | 100110 | +| 40 | FFS | FFS | 100111 | + +DWLCH ID is a part of WRPCT-ID (see clause B.1.3.2.2), which is transmitted downstream within the OC structure of the PSB field. + +###### **B.1.3.2.4 Upstream wavelength channel identifier** + +In a WRP system, upstream wavelength channel ID (UWLCH ID) is a 6-bit number that identifies an upstream wavelength channel and is equal to the ordinal number of the channel defined in Table A.3, converted to the range from 0 to 39, as shown in Table B.2. + +**Table B.2 – UWLCH ID to channel mapping** + +| Channel | Frequency (THz) | Wavelength (nm) | UWLCH ID | +|----------------|------------------------|------------------------|-----------------| +| 1 | 191.5 | 1 565.496 | 000000 | +| 2 | 191.6 | 1 564.679 | 000001 | +| 3 | 191.7 | 1 563.863 | 000010 | +| 4 | 191.8 | 1 563.047 | 000011 | +| 5 | 191.9 | 1 562.233 | 000100 | +| 6 | 192.0 | 1 561.419 | 000101 | +| 7 | 192.1 | 1 560.606 | 000110 | +| 8 | 192.2 | 1 559.794 | 000111 | +| 9 | 192.3 | 1 558.983 | 001000 | +| 10 | 192.4 | 1 558.173 | 001001 | +| 11 | 192.5 | 1 557.363 | 001010 | +| 12 | 192.6 | 1 556.555 | 001011 | +| 13 | 192.7 | 1 555.747 | 001100 | +| 14 | 192.8 | 1 554.940 | 001101 | +| 15 | 192.9 | 1 554.134 | 001110 | +| 16 | 193.0 | 1 553.329 | 001111 | +| 17 | 193.1 | 1 552.524 | 010000 | +| 18 | 193.2 | 1 551.721 | 010001 | +| 19 | 193.3 | 1 550.918 | 010010 | +| 20 | 193.4 | 1 550.116 | 010011 | +| 21 | FFS | FFS | 010100 | +| 22 | FFS | FFS | 010101 | +| 23 | FFS | FFS | 010110 | +| 24 | FFS | FFS | 010111 | +| 25 | FFS | FFS | 011000 | +| 26 | FFS | FFS | 011001 | +| 27 | FFS | FFS | 011010 | +| 28 | FFS | FFS | 011011 | +| 29 | FFS | FFS | 011100 | +| 30 | FFS | FFS | 011101 | +| 31 | FFS | FFS | 011110 | +| 32 | FFS | FFS | 011111 | +| 33 | FFS | FFS | 100000 | +| 34 | FFS | FFS | 100001 | +| 35 | FFS | FFS | 100010 | +| 36 | FFS | FFS | 100011 | +| 37 | FFS | FFS | 100100 | +| 38 | FFS | FFS | 100101 | +| 39 | FFS | FFS | 100110 | +| 40 | FFS | FFS | 100111 | + +UWLCH ID is a part of WRPCT-ID (see clause B.1.3.2.2), which is transmitted upstream within the OC structure of the PSB field. + +###### B.1.3.2.5 ONU identifier + +In a WRP system, the ONU identifier (ONU-ID) is an 8-bit identifier. + +The ONU-ID is unique across the optical distribution network (ODN). When an ONU enters the Initial state (O1) of the ONU activation state machine, it discards the previously assigned ONU-ID along with all dependent WRP TC layer configuration assignments. The semantics of the ONU-ID values is shown in Table B.3. + +**Table B.3 – ONU-ID values** + +| ONU-ID | Designation | Comment | +|---------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0..63 | Assignable | Advertised by OLT CT at ONU activation; used to identify the sender of an upstream transmission or a PLOAMu message and the recipient of a PLOAMd message. | +| 64..254 | Reserved | The number shall not be assigned to any ONU, and shall not be used as an ONU-ID. | +| 255 | Unassigned | Unassigned ONU in PLOAMu. | + +###### B.1.3.2.6 Channel partition index + +An operator may subdivide the set of WDM channels in a WRP system into non-overlapping subsets using an arbitrary criterion, such as commonality of service profile, equipment or geographical location. Each such channel subset is known as a channel partition and is identified by an index which is unique within the WRP system. Channel partition index (CPI) is contained in the Channel\_Profile PLOAM message. + +As an operational attribute, an ONU carries a channel partition index, storing it in a non-volatile memory and ensuring that its value is retained through ONU reactivation, warm and cold reboot, power cycle, management information base (MIB) reset and/or power loss. The value of ONU's CPI is read/write-accessible via OMCI. If the OLT changes the ONU's specific CPI value via OMCI, the OLT is expected to reactivate the ONU immediately thereafter. The ONU's CPI value is only checked against the current channel partition at the start of an activation cycle. + +An ONU's CPI can be specific (non-zero) or default (zero). An ONU with a specific CPI may activate only on channels whose Channel\_Profile CPI matches the CPI of the ONU. An ONU with a default CPI can attempt to activate on a channel belonging to any channel partition, and learns its specific channel partition association at the time of ONU-ID assignment. An ONU with a specific CPI refuses an instruction to tune to a channel belonging to a different channel partition than that of the ONU. + +### B.2 TC layer structure and sublayer functions + +#### B.2.1 WDM PON management TC layer structure + +The WDM PON management TC is implemented at both the OLT and ONU sides of a WRP system. In both downstream and upstream directions, it interfaces with the PMD or the transcoder as a continuous bitstream, which is partitioned into cyclic frames. The downstream and upstream frames have the same format. + +The WDM PON management TC layer is composed of three sublayers: the management TC service adaptation sublayer, the management TC framing sublayer and the management TC PHY adaptation sublayer. Figure B.2 shows the key transformation stages involved in the mapping between the upper layer management data units (MDUs) and the physical interface (PHY) or transcoder bitstream for the downstream and the upstream directions in WDM PON system. Note that MDUs may carry OMCI + +messages, OAM messages, XML-formatted data and other management data units. Also, note that the FEC function is optional and in the transparent mode is applicable to the WDM PON management TC path only. + + + +The diagram illustrates the mapping of Management Data Units (MDUs) for the WDM PON management TC channel across four sublayers: + +- Management TC service adaptation sublayer:** Multiple MDUs are shown at the top. Below them, the data is encapsulated into XGEM frames. Each XGEM frame consists of a header (H) and a payload. Some frames are labeled 'XGEM payload', and one is labeled 'XGEM idle'. The XGEM frames are then mapped into a 'WDM PON mngr payload'. +- Management TC framing sublayer:** The 'WDM PON mngr payload' is framed by an 'MNNGT header' and an 'MNNGT trailer' to form a 'WDM PON mngr frame'. +- Management TC PHY adaptation sublayer:** The 'WDM PON mngr frame' is further processed into 'FEC data' blocks, each followed by a parity bit (P). These are then mapped into a 'WDM PON mngr PHY frame payload'. +- Management TC service adaptation sublayer (bottom):** The 'WDM PON mngr PHY frame payload' is shown at the bottom, framed by 'PSB' (Physical Service Boundary) markers. + +Legend: +H-XGEM frame header +P-FEC parity + +G.9802.2(23) + +Diagram illustrating MDU mapping for WDM PON management TC channel across four sublayers: Management TC service adaptation, Management TC framing, Management TC PHY adaptation, and Management TC service adaptation. The diagram shows the flow of data from multiple MDUs through XGEM frames, WDM PON management payloads, and finally into the physical layer with FEC data and PSB markers. + +**Figure B.2 – MDU mapping for WDM PON management TC channel** + +#### B.2.2 Management TC sublayer functions + +##### B.2.2.1 Management TC service adaptation sublayer + +The WDM PON management TC service adaptation sublayer is responsible for the upper layer MDU encapsulation, multiplexing and delineation in the course of transmission in WDM PON. + +On the transmitter side, the management TC service adaptation sublayer accepts MDUs from the clients, performs MDU fragmentation as necessary, assigns a XGEM Port-ID to an MDU or MDU fragment and applies the XGEM encapsulation method to it to obtain a XGEM frame. The XGEM frame payload can be optionally encrypted. A series of XGEM frames form a payload of the management TC frame. + +On the receiver side, the management TC service adaptation sublayer accepts the payload of the management TC frames, performs XGEM frame delineation, filters XGEM frames based on the XGEM Port-IDs, decrypts the XGEM payload if encryption has been performed by the transmitter, reassembles the fragmented MDUs and delivers the MDUs to the respective clients. + +See clauses 9.1 and 9.2 of [ITU-T G.9804.2] for the details of XGEM framing and XGEM frame delineation, respectively. MDU fragmentation follows procedures for SDU fragmentation (see clause 9.3 of [ITU-T G.9804.2]). + +##### B.2.2.2 Management TC framing sublayer + +The management TC framing sublayer is responsible for the construction and parsing of the overhead fields that support the necessary PON management functionality. The management TC framing sublayer formats are devised so that the frames and their elements are aligned to 4-byte word boundaries, whenever possible. + +On the transmitter side, the management TC framing sublayer accepts the payload from the management TC service adaptation sublayer, and constructs the management TC frames by providing the overhead fields for the embedded operation, administration and maintenance (OAM) and the Physical layer operation, administration and maintenance (PLOAM) messaging channels. + +On the receiver side, the management TC framing sublayer accepts the management TC frames, parses the management TC management information, extracts the incoming embedded management and PLOAM messaging flows and delivers the management TC management payloads to the service adaptation sublayer. The incoming PLOAM messages are delivered to the PLOAM processor. The embedded OAM information is delivered to the control entities outside of the framing sublayer. + +##### B.2.2.3 Management TC PHY adaptation sublayer + +The management TC PHY adaptation sublayer encompasses functions that modify the bitstream modulating the optical transmitter with the goal to improve the detection, reception and delineation properties of the signal transmitted over the optical medium. + +On the transmitter side, the management TC PHY adaptation sublayer accepts the TC frames from the framing sublayer, optionally performs FEC encoding, performs scrambling of the content, prepends the physical synchronization block and provides timing alignment of the resulting bitstream. + +On the receiver side, the management TC PHY adaptation sublayer performs physical synchronization and delineation of the incoming bitstream, descrambles the content of the PHY frame, optionally performs FEC decoding, delivering the resulting management TC frames to the management TC framing sublayer. + +The use of FEC improves the effective sensitivity and overload characteristics of the optical receiver. FEC is for further study. + +Outline of the WDM PON management TC information flow is illustrated in Figure B.3. + + + +Figure B.3: Outline of WDM PON TC management information flow. The diagram shows three layers of information flow. Layer (1) at the bottom is the WDM PON management TC PHY adaptation sublayer, containing 'PHY timing and profile control'. Layer (2) is the WDM PON management TC framing sublayer, containing 'PLOAM partition', 'Embedded OAM fields', and 'XGEM partition'. Layer (3) is the WDM PON management service adaptation sublayer, containing 'PLOAM processor', 'Functions: PM Security key mgmt', and four adapters: 'OMCI adapter', 'ETH OAM adapter', 'XML adapter', and 'Other MNGT adapter'. Above the adapters are four clients: 'OMCI client', 'ETH OAM client', 'XML client', and 'Other MNGT client'. Arrows indicate the flow of information between clients, adapters, the XGEM engine, the framing sublayer partitions, and the PHY control. + +- (1) WDM PON management TC PHY adaptation sublayer +- (2) WDM PON management TC framing sublayer +- (3) WDM PON management service adaptation sublayer + +G.9802.2(23) + +**Figure B.3 – Outline of WDM PON TC management information flow** + +#### B.2.3 WDM PON management TC management functions + +The ONU control, operation and management information in a WDM PON system is carried over three channels: embedded OAM, PLOAM and OMCC. The embedded OAM and PLOAM channels manage the functions of the PMD and WDM PON management TC layers. The OMCC carries the messages of the OMCI protocol, which provides a uniform system for managing higher (service-defining) layers. The characteristics of these channels mimic those of the TWDM-TC layer (as detailed in clauses 8, 9 and 10 of [ITU-T G.989.3]), with some modifications. + +It is also possible to carry other management traffic over the management TC payload, as the content of XGEM frames. The functionality and use of such messages is out of the scope of this Recommendation. + +In addition, the inter-CT communication channel carrying the inter-channel-termination protocol (ICTP) primitives supports the multiple-wavelength aspect of the WDM PON system operation. + +### B.3 WDM PON management framing sublayer + +This clause specifies the structure of the WDM PON management frame along with the format of the header and trailer. + +The format of WDM PON management frame is the same in both the downstream and the upstream directions. It consists of the WDM PON management header, WDM PON management payload and WDM PON management trailer. The WDM PON management payload is formed on the transmit side (OLT CT in the downstream direction, ONU in the upstream direction) and is processed on the receive side (ONU in the downstream direction, OLT CT in the upstream direction) by the corresponding WDM PON management service adaptation sublayer entity. Figure B.4 illustrates the WDM PON management frame format. + + + +The diagram illustrates the structure of a WDM PON management frame. It is divided into three main sections: Management header, WDM-PON management payload, and Management trailer. The Management header is further detailed with fields: PLOAM count (8 bits), Payload length (16 bits), SFC offset (17 bits), Ind (10 bits), HEC (13 bits), and PLOAM partition (0 or 48 × count bits). The Ind field is further detailed with fields: Reserved (6 bits), Engaged (1 bit), LOMC (1 bit), FWI (1 bit), and DG (1 bit). The Management trailer contains the BIP (4 bytes) field. + +| | | | | | | | | +|-----------------------|---------------------------|-----------------------|------------------|----------------|-----------------------------------------|----------------------------|--------------------| +| Management header | | | | | | WDM-PON management payload | Management trailer | +| PLOAM count
8 bits | Payload length
16 bits | SFC offset
17 bits | Ind
10 bits | HEC
13 bits | PLOAM partition
0 or 48 × count bits | | BIP
4 bytes | +| | | Reserved
6 bits | Engaged
1 bit | LOMC
1 bit | FWI
1 bit | | | + +G.9802.2(23) + +Diagram of WDM PON management frame format showing Management header, WDM-PON management payload, and Management trailer with detailed bit fields. + +Figure B.4 –WDM PON management frame format + +#### B.3.1 PLOAM count + +This field contains an 8-bit unsigned integer, indicating the number of PLOAM messages in the PLOAM partition. + +#### B.3.2 Payload length + +This field contains a 16-bit unsigned integer, indicating size of the WDM PON management payload, measured in 4-byte words. + +#### B.3.3 SFC offset + +This field represents the offset in nanoseconds between the instant that the superframe counter (SFC) has been most recently incremented and the instant the first bit of the WDM PON management frame is transmitted. + +Together with the SFC value carried within the PSB, the SFC offset represents the start time of a WDM PON management PHY frame. The ONU uses this information to synchronize with the OLT; the OLT may use this information to estimate the round-trip delay of the ONU. + +#### **B.3.4 Ind field** + +The indication (Ind) field has ten bits that provide fast signalling and are allocated as follows. + +Bits 9 – 4: Reserved, set to 000000 by the transmitter and ignored by the receiver. + +Bit 3: Reserved. + +Bit 2: Loss of management channel (LOMC) flag indicating loss of synchronization to the received AMCC by the sender of the management frame. + +Bit 1: Reserved - usage is for further study. + +Bit 0 (LSB): Dying gasp (DG); When this bit is set, it indicates that the ONU has detected a local condition that may prevent the ONU from transmitting upstream. This indication may assist the OLT in distinguishing fibre plant problems from premises issues. Sending a DG indication does not necessarily constitute a commitment or intent on the part of ONU to cease transmitting. If the condition that has led to DG indication does not persist, the ONU revokes the indication and continues operation. For upstream use and set to 0 in the downstream WDM PON management frame. + +#### **B.3.5 HEC field** + +The error detection and correction field for the upstream framing sublayer (FS) header is a combination of a truncated BCH(63, 12, 2) code operating on the 31 initial bits of the header and a single parity bit. The details of the hybrid error correction (HEC) construction and verification are specified in Annex G. + +#### **B.3.6 PLOAM partition** + +Refer to clause B.7.2. + +#### **B.3.7 WDM PON management frame trailer** + +The WDM PON management frame trailer contains a 4-byte bit-interleaved even parity (BIP) field computed over the entire management frame. Note: The ONU and OLT CT uses the FS frame trailer (BIP) to estimate the BER of the management PHY link. If FEC is supported in management channel in PHY adaptation sublayer, the ONU uses the FEC correction results to obtain the BER of the management PHY link. + +#### **B.3.8 XGEM port identifier** + +The XGEM port identifier, or XGEM Port-ID, is a 16-bit number that is assigned by the OLT CT to an individual logical connection. The XGEM Port-ID assignment to the OMCC logical connection is implicit by virtue of the ONU-ID assignment to the given ONU. The OMCC Port-ID is numerically equal to the respective ONU-ID. + +The semantics of the XGEM Port-ID values is shown in Table B.4. + +**Table B.4 – XGEM Port-ID values** + +| XGEM Port-ID | Designation | Comment | +|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| 0..63 | Default | Default XGEM Port-ID, which is implicitly assigned with and is equal to the ONU-ID. It identifies the XGEM port used by the OMCC traffic. | +| 64...65534 | Reserved | The number shall not be assigned by any OLT CT, and not be used as XGEM Port-ID. | +| 65535 | Idle | Reserved for Idle XGEM Port-ID | + +### B.4 Management TC PHY adaptation sublayer + +This clause discusses matters of physical synchronization and delineation, forward error correction and transcoding for the transmission at the WDM PON management TC PHY adaptation sublayer. + +#### B.4.1 Management TC PHY frame + +An in-service WDM PON OLT CT or ONU is continuously transmitting. The transmission is partitioned into management TC PHY frames. The duration of a management TC PHY frame is a flexible period. A management TC PHY frame consists of a 24-byte physical synchronization block (PSB) and a PHY frame payload. The PHY payload is represented by the management TC frame whose content is optionally protected by FEC. + +The start of a particular PHY frame is defined in the context of the given network element and corresponds to transmission (by the OLT CT) or receipt (by the ONU) of the first bit of its PSB. + +##### B.4.1.1 Physical synchronization block (PSB) + +The WDM PON PSB structure shown in Figure B.5 has the same structure as the TWDM PSBd structure. The physical synchronization sequence (PSync) contains a fixed 64-bit pattern. The OLT CT and ONU use this sequence to achieve alignment at the boundary of the upstream and downstream PHY frame, respectively. The coding of the PSync field is 0xC5E51840 FD59BB49. + + + +``` + +graph TD + PSB[PSB] --> PSync[PSync 8 bytes] + PSB --> SFC[SFC structure 8 bytes] + PSB --> OC[OC structure 8 bytes] + SFC --> SC[Superframe counter 51 bits] + SFC --> HEC[HEC 13 bits] + OC --> OB[OC body 64 bits] + +``` + +G.9802.2(23) + +Diagram of the Physical synchronization block (PSB) structure. The PSB is a 24-byte block divided into three 8-byte fields: PSync, SFC structure, and OC structure. The SFC structure is further divided into a 51-bit Superframe counter and a 13-bit HEC. The OC structure is divided into a 64-bit OC body. + +**Figure B.5 – Physical synchronization block (PSB)** + +##### B.4.1.2 Superframe counter structure + +The SFC structure is a 64-bit field that contains a 51-bit superframe counter (SFC) and a 13-bit HEC field (see Figure B.5). The SFC is maintained by the OLT CT and is incremented by one every PHY frame. Whenever the SFC reaches its maximum value (all ones), it is set to 0 on the next increment operation. + +The SFC structure in a downstream management TC frame is populated with OLT CT's SFC value at the moment the first bit of the frame is transmitted. Note that the SFC values in consecutive management TC frames are not necessarily represented by consecutive integers. A WDM PON management TC frame also carries the SFC offset (see clause B.3.3), which provides the length of + +the time interval between the instant the SFC has been incremented and the moment the first bit of the frame is transmitted. + +The ONU uses the SFC and SFC offset in a received downstream management TC frame to set its own copy of the SFC. The ONU increments its copy of the SFC every PHY frame using a local clock source in-between downstream management TC frames and may adjust its copy of the SFC to the OLT CT's value each time a downstream management frame is received. + +##### B.4.1.3 Operation control structure + +The OC structure contains a 64-bit OC body (see Figure B.6) which has the particular format described below and is filled in by the OLT CT in accordance with explicitly specified data. + + + +Figure B.6 – Operation control structure in WDM PON management TC PHY frame. The diagram shows a hierarchical breakdown of the 64-bit OC body. The top level is 'OC body 64 bits'. The second level breaks it down into 'PIT 21 bits', 'PON-ID 32 bits', 'R 1bit', 'C 1bit', and 'TOL 9 bits'. The third level further breaks down the 'PIT 21 bits' into 'RE 1bit', 'ODN class 3 bits', 'DS FEC 1 bit', 'P 1bit', and 'Link type ext 15 bits'. The 'PON-ID 32 bits' is further broken down into 'Administrative label 24 bits' and 'ONU-ID 8 bits'. A label 'G.9802.2(23)' is present at the bottom right. + +Figure B.6 – Operation control structure in WDM PON management TC PHY frame + +The OC structure is shown in Figure B.6 and the content of the WRP OC body as follows: + +**PIT**, or **PON-ID type** (21 bits, static, provisioned by the operator): an indication of the ODN architecture, the source of the reported launch power and the ODN class. The PON-ID type (PIT) field is further partitioned as follows: + +- **RE flag** (1 bit): indicates whether the transmit optical level (TOL) field contains the launch power of the OLT (RE = 0) or of a reach extender (RE = 1). +- **ODN class** (3 bits): identifies the nominal optical parameters of the transceiver according to ODN optical path loss (OPL) class as defined in Table B.5 reusing [ITU-T G.985] and [ITU-T G.989.3] code values. + +Table B.5 – ODN optical path loss (OPL) class encoding + +| Code value | ODN OPL class | +|------------|---------------| +| 000 | X | +| 001 | Y | +| 010 | Reserved | +| 011 | Reserved | +| 100 | Reserved | +| 101 | Reserved | +| 110 | Reserved | +| 111 | Reserved | + +- **DS FEC flag** (1 bit): Indicates whether FEC is enabled in the downstream direction. When this bit is set to 1, the FEC of the carried downstream channel is enabled. When this bit is set to 0, the FEC of the carried downstream channel is disabled. +- **P flag** (1 bit): Initially set to zero, the P flag is set when an ONU has been detected and round-trip delay confirmation is expected from the ONU. +- **Link type ext** (15 bits): The link type "extended" is segmented in two sections. + - **Distance estimation** (13 bits): Set to zero by default, it contains upon reception of a valid answer from an ONU the estimated distance between the OLT and ONU in multiple of 10 m. 13 bits enable to cover up to 80 km. + - **Link type legacy** (2 bits): reserved + +NOTE – This two-bit field inherited from PON OC could be used to indicate the ITU-T G.9802 mode (transparent or transcoded, or data rate or else ...) and the type of application/terminal supported by the OLT. This application remains for further study. + +**PON-ID** (32 bits, static, provisioned by the operator): identifies the WDM PON channel termination within a certain domain. PON-ID consists of two fields: + +- **Administrative label**: 24-bit field, assigned by EMS/OSS in accordance with some certain physical or logical numbering plan. The Administrative Label is treated transparently by the OLT CT; +- **ONU-ID**: 8-bit field, used in upstream WDM PON management PHY frame. + +**TOL** (9 bits, dynamic, maintained by the system): Transmit optical level. An indication of the current OLT transceiver channel launch power into the ODN (at the S/R reference point), if RE = 0, or reach extender transceiver launch power, if RE = 1. Its value is an integer representing a logarithmic power measure having 0.1 dB granularity with respect to –30 dBm (i.e., the value zero represents –30 dBm, 0x12C represents 0 dBm, and 0x1FE represents 21 dBm). The 0x1FF default value indicates that TOL is not supported on the given WRP interface. + +#### B.4.2 WDM PON Management frame synchronization + +The WDM PON management TC frames are transmitted with the specified format, and the receiver must process these to locate the frame boundaries to facilitate further processing. While the details of the synchronization mechanism are internal to the receiver and are not subject to standardization, the following description represents the reference synchronization state machine that is reasonably immune to both false lock (on an independent uniformly random bitstream) and false loss of synchronization. The vendor implementation of the receiver synchronization mechanism is expected to match the performance of the reference state machine. + +The reference implementation of the receiver synchronization state machine is shown in Figure B.7. + +The receiver begins in the Hunt state. While in the Hunt state, the receiver searches for the PSync pattern in all possible alignments (both bit and byte) within the signal. Once an exact match with the PSync pattern specified in clause B.4.1.1 is found, the receiver verifies if the 64 bits immediately following the PSync pattern form a valid (i.e., error-free or correctable) HEC-protected SFC structure (see Table A.4 of [ITU-T G.987.3] for the HEC verification rules). If the 64-bit protected SFC structure is uncorrectable, the receiver remains in the Hunt state and continues searching for a PSync pattern. If the 64-bit protected SFC structure is valid, the receiver transitions into the PreSync state. + + + +``` + +stateDiagram-v2 + [*] --> Hunt + Hunt --> Pre-Sync: Exact PSync match and SFC usable + Pre-Sync --> Sync: Both PSync and SFC verified + Sync --> Sync: Both PSync and SFC verified + Sync --> Re-Sync: PSync and/or SFC fails + Re-Sync --> Hunt: M-1 consecutive PSync and/or SFC failures + Re-Sync --> Sync: Both PSync and SFC verified + Re-Sync --> Re-Sync: PSync and/or SFC fails + +``` + +G.9802.2(23) + +Figure B.7 – Synchronization state machine at the receiver side. The diagram shows four states: Hunt state, Pre-Sync state, Sync state, and Re-Sync state. Transitions are based on PSync and/or SFC verification results. The Hunt state is the initial state. Transitions from Hunt to Pre-Sync occur on an exact PSync match and SFC usability. Transitions from Pre-Sync to Sync occur when both PSync and SFC are verified. Transitions from Sync to Re-Sync occur if PSync and/or SFC fails. Transitions from Re-Sync to Hunt occur after M-1 consecutive failures. Transitions from Re-Sync to Sync occur if both PSync and SFC are verified. Self-loops on Sync and Re-Sync states indicate continued verification. + +**Figure B.7 – Synchronization state machine at the receiver side** + +Once the receiver locates a boundary of a PHY frame and leaves the Hunt state, it performs PSync and SFC verification on each subsequent PHY frame boundary. The following PHY frame boundary is located $9 + \text{PLOAM\_count} \times 12 + \text{Payload\_len}$ words later in the signal bitstream. The PSync verification is successful if at least 62 bits of the incoming 64-bit sequence match the fixed PSync pattern; otherwise, the PSync verification fails. The SFC verification is successful if the incoming 64-bit sequence forms a valid (error-free or correctable) HEC-protected field. + +Once in the Pre-Sync state, the ONU transitions to the Sync state if both PSync verification and SFC verification are successful, and returns to the Hunt state if either PSync verification or SFC verification fails. + +Once in the Sync state, the receiver remains in that state as long both PSync verification and SFC verification are successful, and transitions into the Re-Sync state, if either PSync verification or SFC verification fails. + +Once in the Re-Sync state, the receiver transitions back to Sync state if both PSync and SFC are successfully verified once. However, if for $M - 1$ consecutive PHY frames either PSync verification or SFC verification fails, the ONU declares loss of downstream synchronization, and transitions into the Hunt state. + +The recommended value of the parameter $M$ is 3. + +#### B.4.3 Forward error correction + +FEC in transparent WDM PON management channel for further study. + +See Annex F for FEC in transcoding WDM PON management channel. + +#### B.4.4 Transcoding + +Transcoding is neither needed nor supported when transmitting the WDM PON management frames using transparent WDM PON management channel. + +Transcoding WDM PON management channel supports the transcoding function in the WDM PON management PHY adaptation sublayer. See Annex E for the involved transcoding procedures. + +### B.5 Management channel and interface + +In WDM PON system, the OAM data is transmitted in auxiliary management and control channel (AMCC), which can be implemented in either transparent mode or transcoding mode. If operator selects one implementation, the interface of the management channel shall be specific. + +For transparent mode, the pilot-tone is used to overlay AMCC onto the data channel (e.g., CPRI and eCPRI transmission). The interfaces and implementations of AMCC Transparent mode shall be based on the mechanisms described in Annex B of [ITU-T G.989.2]. + +For transcoded mode, the implementations depend on the line coding and FEC code of the data transmission channel. The interfaces and implementations of AMCC transcoding mode shall be based on the mechanisms described in Annex E and Annex F. + +### B.6 Channel management (per channel, per channel group, and inter-channel management) + +This clause contains the procedural specification of the profile announcement function: + +#### B.6.1 Overview + +The profile announcement in a WDM PON system is transmitted in a form of a series of unacknowledged unassigned ONU-IDPLOAM messages on each downstream wavelength channel and consists of: + +- a single System\_Profile PLOAM message; +- a set of Channel\_Profile PLOAM messages, one per deployed channel pair. + +The complete set of profiles is distributed periodically with the period TminProfile, which can be set between 1 and 5 seconds. + +A channel profile consists of a block of common parameter, a downstream wavelength channel descriptor, and an upstream wavelength channel descriptor. + +A Channel\_Profile message can include parameters for both of a downstream wavelength channel and an upstream wavelength channel. + +Each Channel\_Profile message specifies a static one-to-one association between the upstream and downstream wavelength channels: an ONU which is listening to the given downstream wavelength channel responds in the given upstream wavelength channel. + +##### B.6.1.1 WDM PON system and channel descriptors + +A system descriptor is a collection of system parameters and their specified values. A System\_Profile PLOAM message carries System parameters. + +**Table B.6 – System descriptor content** + +| Parameter | Description | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Channel count | The number of WDM PON channels with distinct channel profile identifiers that exist in the system.
NOTE – Each channel is counted once, regardless of the number of its peer CTs in any protection scheme. | +| MSE | Maximum spectral excursion represented as an unsigned integer indicating the value in units of 1 GHz. | + +A wavelength channel descriptor is a collection of parameters and their specified values pertaining to the downstream and upstream wavelength channels. A Channel\_Profile PLOAM message carries channel profile parameter set. + +**Table B.7 – Channel profile elements** + +| Parameter | Description | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Common parameters | | +| Channel profile identifier | Channel profile identification that must be unique for each WDM PON channel that exists in the system. The total number of channel profiles is set by the Channel count of the system descriptor (see Table B.6). | +| AMCC type | Indicates whether the AMCC is transported in the transparent or transcoded mode. | +| Protection flag | The flag is set if and only if the profile pertains to a WDM PON channel to be used for protection. (For further study) | +| PON-ID | A 32-bit static value which is carried in the OC structure and uniquely identifies a WDM PON channel termination (CT) entity within a domain. | +| Downstream wavelength channel descriptor | | +| DWLCH ID | Assigned downstream wavelength channel ID. | +| Downstream line rate | The specification of the data rates supported by the OLT in the given wavelength channel in the downstream direction.
In a profile of this channel this parameter is included for reference only, as the ONU already knows the value when receiving the message. | +| Downstream FEC indication | Downstream FEC ON/OFF indicator.
In a profile of this channel this parameter is included for reference only, as the ONU already knows the value when receiving the message. | +| Channel partition index | An index of the operator-specified channel subset in an WDM PON system. During operation, the ONUs can be re-tuned between the channels within a channel partition, but not across the boundaries of the channel partition. | +| Upstream wavelength channel descriptor | | +| UWLCH ID | Assigned upstream wavelength channel identifier. | +| Upstream frequency | The frequency specification of the upstream wavelength channel: a single nominal central frequency, or a root frequency of a cyclic set of nominal central frequencies forming an upstream wavelength channel. | +| Optical link type | Upstream optical link type described in the Link type ext. field of the OC structure in clause B.4.1.3 | +| Upstream line rate | The specification of the data rates supported by the OLT in the given wavelength channel in the upstream direction. | +| PON-TAG digest | A cryptographic hash over the public PON-TAG value computed using a shared secret. | + +##### B.6.1.2 Profile parameter learning by ONU + +An OLT CT transmits each component of the profile announcement at regular intervals, frequently enough to ensure proper operation of the ONUs. The transmission frequencies of the individual profile announcement components should be reasonably consistent; however, strict periodicity and phase alignment are not required. + +In order to be able to activate on the WDM PON system, an ONU should receive and process at least: the System\_Profile PLOAM message, a Channel\_Profile PLOAM message for the downstream wavelength channel and the upstream wavelength channel the ONU intends to operate on. + +The ONU begins learning the system, and channel, profile parameters once it reaches state O1.2 of the ONU activation cycle state machine, and continues learning the profile parameters through the activation cycle, as long as it stays synchronized to the downstream PHY frames. + +The ONU retains the system and channel profile parameters through the completion of the activation cycle, unless it enters state O1.1 from state O7, that is, recovers from Emergency Stop state (O7). In the latter case, the system and channel profile parameters are discarded. + +### **B.7 WDM PON PLOAM messaging channel** + +#### **B.7.1 Overview** + +The physical layer OAM (PLOAM) messaging channel in a WDM PON system is an operations and management facility between OLT CTs and ONUs that is based on a fixed set of 48-byte messages transported within a designated field of the XGTC frame header (downstream) and the XGTC header (upstream). The OLT CT and ONU PLOAM processors appear as clients of the respective management TC framing sublayers. The PLOAM channel provides more flexible functionality than the embedded management channel and is generally faster than the OMCC. + +##### **B.7.1.1 PLOAM channel functionality** + +The PLOAM channel supports the following WDM PON TC layer management functions: + +- Profile announcement; +- ONU activation; +- ONU registration; +- Power management. + +##### **B.7.1.2 PLOAM channel rate limitations** + +Downstream PLOAM messages fall into two categories, the messages that are transmitted to unactivated ONUs associated with the given OLT CT, and the messages that are unicast to a specific ONU identified by its ONU-ID. Within a given frame, the OLT CT may transmit at most one PLOAM message to each ONU. + +The ONU should be able to store eight downstream PLOAM messages before they are processed. The PLOAM processing model is single threaded. The normative processing time of a PLOAM message is 6 PHY frame duration. That is, once a downstream PLOAM message is received in an empty queue in downstream PHY frame $N$ , the ONU should be able to remove the message from the queue, perform all associated processing and generate a response to be sent upstream not later than in upstream PHY frame $N+6$ . Furthermore, if at the start of the upstream frame in which a PLOAM response is sent upstream, the PLOAM queue remains not empty, the message at the head of the queue should be processed and the response, if required for the given message type, be prepared for upstream transmission not later than in the 6th subsequent upstream PHY frame. + +Note that under these requirements, the OLT CT can determine the maximum number of unacknowledged PLOAM messages directed to a given ONU as well as the expected response time for any downstream PLOAM message. + +##### **B.7.1.3 PLOAM channel robustness** + +When as a result of unicast PLOAM message processing the ONU enters or remains in the Operation state (O5), it acknowledges the processing outcome by generating an upstream PLOAM message. (See clause B.8 for the ONU activation cycle states and transitions.) Such a response PLOAM can be either of a specific type required by the particular PLOAM protocol, or of the general Acknowledgement type. An Acknowledgement PLOAM message is generated also in case of a downstream PLOAM format or processing error. Both a specific type response and the Acknowledgement type response carry the sequence number of the downstream message being + +acknowledged. In addition, the Acknowledgement type response carries a completion code that indicates the outcome of PLOAM message processing. + +Moreover, a PLOAM message of Acknowledgement type is used in response to a PLOAM allocation when no upstream PLOAM is available for transmission. In this case, the completion code allows to distinguish between the idle condition (no PLOAM message in the transmit queue or being processed) and the busy condition (the PLOAM upstream transmit queue is empty, but a downstream PLOAM message is being processed). + +Downstream PLOAM messages that fail the integrity check are not acknowledged. + +If the OLT CT expects the ONU to acknowledge or respond to a message, and instead receives merely a keep-alive acknowledgement to a PLOAM request, it can infer that the ONU has failed to process the message. If ONUi repeatedly fails to acknowledge a downstream PLOAM message, the OLT CT detects the LOPCi defect. + +##### B.7.1.4 Extensibility + +The implementation of the PLOAM channel should be flexible to accommodate future enhancements in a backward-compatible way. + +#### B.7.2 PLOAM message format + +The PLOAM message structure is shown in Table B.8, with each field being further defined in the following clauses. + +**Table B.8 – Generic PLOAM message structure** + +| Octet | Field | Description | +|-------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1-2 | ONU-ID | Eight bits, aligned at the least significant bit (LSB) end of the 2-byte field. The eight most significant bits are reserved, and should be set to 0 by the transmitter and ignored by the receiver. | +| 3 | Message type ID | This byte indicates the message type. The enumerated code point for each message type is defined below. | +| 4 | SeqNo | Sequence number. | +| 5-40 | Message_Content | The message content is defined in the clause that describes each message type ID. | +| 41-48 | MIC | Message integrity check. | + +##### B.7.2.1 ONU-ID + +The ONU-ID field includes eight reserved bits, plus an actual 8-bit ONU identifier that specifies the message recipient in the downstream direction or the message sender in the upstream direction. During ONU activation, the ONU is assigned an ONU-ID in the range from zero to 63. The reserved ONU-ID value 255 (0x00FF) indicates a message to un-activated ONU in the downstream direction or an ONU that has not been assigned an ONU-ID in the upstream direction. + +##### B.7.2.2 Message type ID + +Message type ID is an 8-bit field that indicates the type of the message and defines the semantics of the message payload. Message type ID code points are defined in clause B.7.3. Message type ID code points that are not explicitly defined in this Recommendation are reserved. Reserved Message type ID code points should not be allocated by any vendor for any purpose and should not be transmitted in a PLOAM message. Upon receipt of an upstream PLOAM message with an unsupported message type ID, an OLT CT should ignore the message, including the sequence number field. Upon receipt of a downstream PLOAM message with a reserved or unsupported message type ID, an ONU should + +ignore the message, if it was sent with the unassigned ONU-ID, or negatively acknowledge the message as an unknown message type, if it was sent to that specific ONU-ID. + +##### **B.7.2.3 SeqNo** + +SeqNo is an 8-bit field containing a sequence number counter that is used to ensure robustness of the PLOAM messaging channel. + +In the downstream direction, the SeqNo field is populated with the value of a corresponding OLT CT sequence number counter. The OLT CT maintains a separate sequence number counter for each ONU PLOAM message flow. For each ONU, the OLT CT initializes the sequence number counter to 1 upon ONU-ID assignment during activation. Upon transmission of a PLOAM message, the appropriate sequence number counter is incremented. Each sequence number counter rolls over from 255 to 1; the value 0 is not used in the downstream direction. + +In the upstream direction, whenever an upstream PLOAM message is a response to a downstream PLOAM message, the content of the SeqNo field is equal to the content of the SeqNo field of the downstream message. The same SeqNo may appear on more than one upstream PLOAM message. If a PLOAM message is originated autonomously by the ONU, the value SeqNo = 0 is used. + +##### **B.7.2.4 Message content** + +Octets five to 40 of the PLOAM message are used for the payload of PLOAM messages. The message payload content is specific to a particular message type ID and is defined in clause B.7.3. Unused octets of the message payload content are padded with the value 0x00 by the transmitting PLOAM processor and are ignored by the receiving PLOAM processor. + +##### **B.7.2.5 Message integrity check** + +The message integrity check (MIC) is an 8-byte field that is used to verify the sender's identity and to prevent a forged PLOAM message attack. + +MIC generation is specified in clause B.11.4. Key generation and management for PLOAM MIC is specified in clause B.11.5. + +For the purpose of MIC verification, there is no distinction between the significant octets and padding octets of the message payload content. Using the PLOAM message content and the shared PLOAM integrity key, the sender computes the MIC and transmits it with the PLOAM message. Using the same message content and shared key, the receiver computes its version of the MIC and compares it with the MIC value carried in the received PLOAM message. If the two MIC values are equal, the PLOAM message is valid. Otherwise, the message is declared invalid and should be discarded. + +The shared PLOAM integrity key can be either ONU-specific, derived based on the master session key (MSK) or default (see clauses B.11.3.1 and B.11.5.1, respectively). The selection of either ONU-specific or default PLOAM integrity keys for each PLOAM message type is specified in clauses B.7.3.3 and B.7.3.4. + +##### **B.7.2.6 Common elements of PLOAM message format** + +###### **B.7.2.6.1 Vendor\_ID** + +Vendor\_ID is the first of the two components of the ONU serial number, which ONU reports to the OLT CT in the course of activation or upon handover, and which the OLT CT stores and subsequently uses to address the ONU when the ONU-ID is not yet available or is considered unreliable. + +The code set for the Vendor\_ID is specified in [b-ATIS-0300220]. + +The four characters are mapped into the 4-byte field by taking each ASCII/ANSI character code and concatenating them. For example, Vendor\_ID = ABCD fills the four octets of the PLOAM message format element as follows: + +| Character | Octet | Value | +|-----------|-------|-------| +| A | 1 | 0x41 | +| B | 2 | 0x42 | +| C | 3 | 0x43 | +| D | 4 | 0x44 | + +###### B.7.2.6.2 VSSN + +Vendor-specific serial number (VSSN) is the second of the two components of the ONU serial number, which ONU reports to the OLT CT in the course of activation or upon handover, and which the OLT CT uses to address the ONU when the ONU-ID is unavailable or unreliable. + +VSSN is a four-byte unsigned integer, selected by the ONU vendor. + +###### B.7.2.6.3 Correlation tag + +For the upstream message types that may have to be transmitted multiple times with varying optical power (Serial\_Number\_ONU), the ONU generates and inserts the Correlation tag into the transmitted message. Once the upstream PLOAM message is received, the OLT CT copies the correlation tag of the successful upstream PLOAM message into the downstream PLOAM response, so that the ONU is able to associate the response with the variable parameters of the successfully transmitted message. + +In an upstream PLOAM message, the correlation tag is an ONU-generated non-zero 16-bit field, which should take a different value each time the transmitter optical power is changed. In a downstream PLOAM message, the correlation tag of all zeros indicates that the message is not sent as a response to an ONU's activation. + +#### B.7.3 PLOAM message definitions + +##### B.7.3.1 Downstream PLOAM message summary + +Table B.9 summarizes the downstream PLOAM messages. + +**Table B.9 – Downstream PLOAM messages** + +| Message type ID | Message name (applicability) | Function | Trigger | Effect of receipt | +|-----------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0x03 | Assign_ONU-ID | To link a free ONU-ID value with the ONU's serial number. | When the OLT CT recognizes the unique serial number of an ONU during the discovery process. | The ONU with the specified serial number sets its ONU-ID and also its default Alloc-ID and OMCC XGEM port-ID. No Acknowledgement. | +| 0x05 | Deactivate_ONU-ID | To instruct a specific ONU to stop sending upstream traffic and reset itself. It can also be an unassigned ONU-ID message. | At the implementor's discretion. | The ONU with the specified ONU-ID switches off its laser. The ONU-ID, default and explicit Alloc-IDs and default XGEM Port-ID are discarded. The ONU transitions to the Initial state (O1). No Acknowledgement. | + +**Table B.9 – Downstream PLOAM messages** + +| Message type ID | Message name (applicability) | Function | Trigger | Effect of receipt | +|-----------------|-----------------------------------|--------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0x06 | Disable_Serial_Number (Invariant) | Unassigned ONU-ID message to disable/enable a specific ONU or a specific ONU set. | At the implementor's discretion. Note that to effectively bring an ONU out of the Emergency Stop state, the Disable_Serial_Number PLOAM message with the Enable option must be transmitted in all available WRP channels. |
The addressed ONUs (that is, the ONU with the specified serial number, or, the tuned-in ONUs in the Serial Number state (O2-3), or all tuned-in ONUs) switch off the laser and transition to the Emergency Stop state (O7). The disabled ONUs are prohibited from transmitting.
Enable option: The addressed ONUs (that is, the ONU with the specified serial number or all tuned-in ONUs in the Emergency Stop state (O7)) transition to the Initial state (O1). The enabled ONUs discard the TC layer configuration and restart the activation, as specified in clause B.8. No Acknowledgement.
| +| 0x09 | Request_Registration | To request an ONU's Registration_ID. | At the implementor's discretion; ONU has been previously activated. | Send the Registration message. | +| 0x12 | Reserved for Sleep Mode | FFS | FFS | FFS | +| 0x17 | System_Profile | Unassigned ONU-ID message containing a copy of the system descriptor (see clause B.6.1.1). | Periodically with programmable periodicity. |The ONU stores the profile information or updates the profile information previously stored for use in subsequent channel management and operation tasks.
No Acknowledgement.
| + +**Table B.9 – Downstream PLOAM messages** + +| Message type ID | Message name (applicability) | Function | Trigger | Effect of receipt | +|-----------------|-------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0x18 | Channel_Profile (Specific message format) | Unassigned ONU-ID message containing a copy of one downstream wavelength channel descriptor and one upstream wavelength channel descriptor (see clause B.6.1.1). | Periodically with programmable periodicity. | The ONU stores the profile information or updates the profile information previously stored for use in subsequent channel management and operation tasks.No Acknowledgement. | +| 0x1C | Rate_Control | To instruct an ONU to change its receive or transmit data rate. | At the OLT's discretion. | The ONU sends acknowledgement and modifies its receive and/or transmit rate according to the instructions. | +| 0x1D | Reboot_ONU | Unassigned ONU-ID or unicast message to cause one or more ONUs to reboot. | At the implementer's discretion. | This is downstream only message and OLT does not expect ACK for this message. All addressed ONUs are expected to reboot. | + +##### B.7.3.2 Upstream PLOAM message summary + +Table B.10 summarizes the upstream messages. + +**Table B.10 – Upstream PLOAM messages** + +| Message type ID | Message name (applicability) | Function | Trigger | Effect of receipt | +|-----------------|--------------------------------------------|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0x01 | Serial_Number_ONU (Specific field formats) | To report the serial number of an activating ONU. | An ONU in the Serial Number state (O2-3) sends a Serial_Number_ONU message after tuning to the correct upstream wavelength to announce its presence on the PON. | The OLT CT detects an activation attempt, discerns the activating ONU's serial number and provides feedback to the activating ONU, which can be in the form of Assign_ONU-ID message. | +| 0x02 | Registration | To report the Registration_ID of an ONU. | When the ONU is in the Operation state (O5) and is responding to the Request_Registration message. | The OLT CT may use the ONU's Registration_ID as described further in clause B.11.2.1. | + +**Table B.10 – Upstream PLOAM messages** + +| Message type ID | Message name (applicability) | Function | Trigger | Effect of receipt | +|-----------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| 0x09 | Acknowledgement | To indicate reception of specified downstream messages, to report PLOAM processing error, or to provide busy or no-message indication. | Upon receipt of a downstream message that requires acknowledgement. | The OLT CT uses a received Acknowledgement PLOAM message to verify integrity of the PLOAM channel with the given ONU. | +| 0x10 | Reserved for Sleep Mode | FFS | FFS | FFS | +| 0x1C | Rate_Response | To respond to the Rate_Control PLOAM message, indicating either the intent or the inability to execute the instruction, along with the applicable response code. | Upon receipt of a Rate_Control message. | The OLT CT either adjusts the line rates according to the instructions, or executes a diagnostic procedure at its discretion. | + +##### B.7.3.3 Downstream PLOAM message formats + +###### B.7.3.3.1 Assign\_ONU-ID message + +Information regarding Assign\_ONU-ID message is provided in Table B.11. + +**Table B.11 – Assign\_ONU-ID message** + +| Octet | Content | Description | +|-------|-------------------|-----------------------------------------------------------------------------------------------------------------------------| +| 1-2 | ONU-ID | 0x00FF, Unassigned ONU-ID ONU-ID. | +| 3 | Message type ID | 0x03, "Assign_ONU-ID". | +| 4 | SeqNo | Eight-bit Unassigned ONU-ID PLOAM sequence number. | +| 5-6 | ONU-ID Assignment | LSB-justified 8-bit assigned ONU-ID value padded with eight most significant bit (MSB) zeros; range 0..63 (0x0000..0x003F). | +| 7-10 | Vendor_ID | See clause B.7.2.6.1. | +| 11-14 | VSSN | See clause B.7.2.6.2. | +| 15-40 | Padding | Set to 0x00 by the transmitter; treated as "don't care" by the receiver. | +| 41-48 | MIC | Message integrity check, computed using the default PLOAM integrity key. | + +###### B.7.3.3.2 Deactivate\_ONU-ID message + +Information regarding Deactivate\_ONU-ID message is provided in Table B.12. + +**Table B.12 – Deactivate\_ONU-ID message** + +| Octet | Content | Description | +|-------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| 1-2 | ONU-ID | Directed message to one ONU or unassigned ONU-ID message to all ONUs. As an unassigned ONU-ID message, ONU-ID = 0x00FF. | +| 3 | Message type ID | 0x05, "Deactivate_ONU-ID". | +| 4 | SeqNo | Eight-bit unicast or unassigned ONU-ID PLOAM sequence number, as appropriate. | +| 5-6 | Reason Code | Reserved for troubleshooting purposes. Set to 0x0000, if not supported or not specified. An aware ONU's action is limited to logging the value. | +| 7-40 | Padding | Set to 0x00 by the transmitter; treated as "don't care" by the receiver. | +| 41-48 | MIC | Message integrity check, computed using the default PLOAM integrity key. | + +###### **B.7.3.3.3 Disable\_Serial\_Number message** + +Information regarding Disable\_Serial\_Number message is provided in Table B.13. + +**Table B.13 – Disable\_Serial\_Number message** + +| Octet | Content | Description | +|-------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1-2 | ONU-ID, | 0x00FF, Unassigned ONU-ID. | +| 3 | Message type ID | 0x06, "Disable_Serial_Number". | +| 4 | SeqNo | Eight-bit unassigned ONU-ID PLOAM sequence number. | +| 5 | Disable/enable |
0xFF: The ONU with this serial number is denied upstream access.
0x00: The ONU with this serial number is allowed upstream access.
0x0F: All tuned-in ONUs are denied upstream access. The content of bytes 6..13 is ignored.
0x3F: Disable_Discovery: the tuned-in ONUs in O2-3 state are denied upstream access. The content of bytes 6..13 is ignored.
0xF0: All tuned-in ONUs are allowed upstream access.
| +| 6-9 | Vendor_ID | See clause B.7.2.6.1. | +| 10-13 | VSSN | See clause B.7.2.6.2 | +| 14-40 | Padding | Set to 0x00 by the transmitter; treated as "don't care" by the receiver. | +| 41-48 | MIC | Message integrity check, computed using the default PLOAM integrity key. | + +###### **B.7.3.3.4 Request\_Registration message** + +Information regarding Request\_Registration message is provided in Table B.14. + +**Table B.14 – Request\_Registration message** + +| Octet | Content | Description | +|-------|-----------------|--------------------------------------------------------------------------| +| 1-2 | ONU-ID | Directed message to one ONU. | +| 3 | Message type ID | 0x09, "Request_Registration". | +| 4 | SeqNo | Eight-bit unicast PLOAM sequence number. | +| 5-40 | Padding | Set to 0x00 by the transmitter; treated as "don't care" by the receiver. | +| 41-48 | MIC | Message integrity check computed using the default PLOAM integrity key. | + +###### B.7.3.3.5 Channel\_Profile message + +Information regarding Channel\_Profile message is provided in Table B.15. + +**Table B.15 – Channel\_Profile message** + +| Octet | Content | Description | +|-------|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1-2 | ONU-ID | 0x00FF, Unassigned ONU-ID. | +| 3 | Message type ID | 0x18, "Channel_Profile". | +| 4 | SeqNo | Eight-bit unassigned ONU-ID PLOAM sequence number. | +| 5 | Control octet | An octet of the form 0AEP 0TDU, where:A – AMCC type indication:
A = 0: Transparent;
A = 1: Transcoded.
E – Engaged flag:
E = 0: Channel is available.
E = 1: Channel has been paired with an ONU.
P – Reserved for Protection (FFS)
T – This channel indicator:
T = 0: The channel profile pertains to another WRP channel.
T = 1: The channel profile pertains to the WRP channel in which it is transmitted (necessarily, D = 0).
D – Downstream void indicator:
D = 0: Downstream descriptor valid.
D = 1: Downstream descriptor to be ignored.
U – Upstream void indicator:
U = 0: Upstream descriptor valid.
U = 1: Upstream descriptor to be ignored.
Flags T, D and U enable a downstream transmission to supply a descriptor for an upstream channel. | +| 6-7 | Channel profile identifier | An identifier which is unique for each WRP channel that exists in the system. | +| 8 | Channel profile version | VVVV 0000, where:
VVVV – Four-bit channel profile version
If the content of the channel profile changes, the OLT CT should ensure that the version also changes, so that the ONU can detect updates solely on the basis of the version field. | + +**Table B.15 – Channel\_Profile message** + +| Octet | Content | Description | +|-------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 9-12 | PON-ID | A 32-bit static value which is carried in the OC structure of each downstream PHY frame in the specified WRP channel (see clause B.4.1.3); consists of 24-bit administrative label (octets 9 and 10 and 11) and ONU-ID (octet 12). | +| 13 | Service type | Type of PtP client service by the channel (WRP) Encoding: For further study. | +| 14-15 | DWLCH ID | Assigned downstream wavelength channel ID. | +| 16-19 | Downstream frequency | The nominal central frequency of the downstream wavelength channel, expressed as an unsigned integer indicating the value in units of 0.1 GHz. | +| 20 | Downstream rate | A bitmap of the form 0000 ABCD indicating the downstream rate support within the WRP channel.
A – Rate class 1 (~10 Gbit/s)
B – Rate class 2 (~25 Gbit/s)
C – Rate class 3 (~50 Gbit/s)
D – Rate class 4 (~100 Gbit/s)
The bit value of 1 indicates that the respective rate class is supported; the bit value of 0 indicates the respective rate class is not supported. | +| 21 | Channel partition | An integer representing the Channel partition index associated with the given Channel_profile. | +| 22-23 | UWLCH ID | Assigned upstream wavelength channel ID. | +| 24-27 | Upstream frequency | The nominal central frequency of the upstream wavelength channel or a root frequency of the cyclic set of central frequencies forming an upstream wavelength channel, expressed as an unsigned integer indicating the value in units of 0.1 GHz. | +| 28 | Upstream rate | A bitmap of the form 0000 ABCD indicating the upstream rate support within the WRP channel.
A – Rate class 1 (~10 Gbit/s)
B – Rate class 2 (~25 Gbit/s)
C – Rate class 3 (~50 Gbit/s)
D – Rate class 4 (~100 Gbit/s)
The bit value of 1 indicates that the respective rate class is supported; the bit value of 0 indicates the respective rate class is not supported. | +| 29-36 | PON-TAG digest | A 64-bit value computed as a cryptographic hash over the public PON-TAG value and the shared secret Registration_ID:
Digest = AES-CMAC(PON-TAG PON-TAG, Registration_ID "PtoPisSimple", 64). | +| 37-40 | Padding | Set to 0x00 by the transmitter; treated as "don't care" by the receiver. | +| 41-48 | MIC | Message integrity check, computed using the default PLOAM integrity key. | + +###### B.7.3.3.6 Reboot\_ONU message + +Table B.16 describes the Reboot ONU message. + +**Table B.16 – Reboot\_ONU message** + +| Octet | Content | Description | +|-------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1-2 | ONU-ID | Directed message to one ONU or unassigned ONU-ID message.
A single ONU is addressed in this message either through an assigned ONU-ID or through Vendor_ID and VSSN with ONU-ID set to 0x00FF (Unassigned ONU-ID).
All ONUs are addressed on the PON when ONU-ID is set to 0x00FF (Unassigned ONU-ID) and Vendor-ID and VSSN fields are set to 0x00. | +| 3 | Message type ID | 0x1D, "Reboot_ONU". | +| 4 | SeqNo | Eight-bit unicast or unassigned ONU-ID PLOAM sequence number, as appropriate. | +| 5-8 | Vendor_ID | See clause B.7.2.6.1. This field is inspected only when ONU-ID is set to 0x00FF (Unassigned ONU-ID). | +| 9-12 | VSSN | See clause B.7.2.6.1. This field is inspected only when ONU-ID is set to 0x00FF (Unassigned ONU-ID). | +| 13 | Reboot depth | This field defines the enumerated values:
0x0 MIB reset (MIB reset is defined in clause 9.1.3 of [ITU-T G.988])
0x1 Perform equivalent of OMCI reboot (clause A.2.35 of [ITU-T G.988])
0x2 Perform equivalent of power cycle reboot
0x3 Configuration reset, then perform MIB reset and reboot*
0x4..0xFF Reserved
*Sometimes ONU may not come up even after OMCI reboot or power-cycle reboot due to saved configuration in the non-volatile memory of the ONUs. When action is set to 0x3, ONU will reset, clear its previously saved configuration (e.g., VoIP configuration and dual managed ONU configuration), perform a MIB reset and then reboot. Factory configuration (serial number and MAC) and registration ID, software images and indication of which image is committed should not be affected by this action.
These mechanisms are intended to be used as a last resort to revive the ONU.
NOTE – Applicable ONU states of the Reboot_ONU PLOAM is up to the implementation. | +| 14 | Reboot Image | This field defines which image will be loaded and executed (i.e., which image will be active) upon reboot using the enumerated values:
0x0 Load and execute the image that is currently committed
0x1 Load and execute the image that is not currently committed
This field is ignored when Reboot depth = 0x0 | +| 15 | ONU State | This field defines the enumerated values:
0x0 Reboot if ONU is in any state
0x1 Reboot only if ONU is in states O1, O2-3 | + +**Table B.16 – Reboot\_ONU message** + +| Octet | Content | Description | +|-------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 16 | Flags | Bits 2-1:
00 Reboot regardless of POTS/VoIP call state
01 Reboot only if no POTS/VoIP calls are in progress
10 Reboot only if no emergency call is in progress
11 Reserved
Bits 8-3: Reserved | +| 17-40 | Padding | Set to 0x00 by the transmitter; treated as "don't care" by the receiver. | +| 41-48 | MIC | Message integrity check, computed using the default PLOAM integrity key. | + +###### **B.7.3.3.7 System\_Profile message** + +Table B.17 describes the System\_Profile message. + +**Table B.17 – System\_Profile message** + +| Octet | Content | Description | +|-------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1-2 | ONU-ID | 0x00FF, Unassigned ONU-ID. | +| 3 | Message type ID | 0x17, "System_Profile". | +| 4 | SeqNo | Eight-bit unassigned ONU-ID PLOAM sequence number. | +| 5-7 | WRPSYS ID | The 20-bit identity of the WDM PON system within a certain domain.
This is a reference value set by the OSS.
The eight LSBs of WRPSYS ID are in Octet 7; the four MSBs of WRPSYS ID are in the LSB nibble of Octet 5. The four MSBs of Octet 5 are zeros. | +| 8 | System profile version | VVVV 0000, where:
VVVV – Four-bit system profile version.
If the content of the system profile changes, the OLT CT should ensure that the version also changes, so that the ONU can detect updates solely on the basis of the version field. | +| 9 | Channel count | 0000 CCCC, where:
CCCC – an unsigned integer indicating the number of channels that exist in the system, each described with a Channel_Profile PLOAM message with a distinct Channel profile identifier. | +| 10 | Channel spacing | An unsigned integer indicating the value in units of 1 GHz.
NOTE – Channel spacing is a system parameter characterizing the grid to which the system is designed, rather than how the wavelength channels are deployed. | +| 11 | Upstream MSE | Maximum spectral excursion (MSE) represented as an unsigned integer indicating the value in units of 1 GHz. | + +**Table B.17 – System\_Profile message** + +| Octet | Content | Description | +|-------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 12-19 | PON-TAG | An 8-byte static attribute of the OLT CT that is chosen by the operator and is used to bind the master session key (MSK) to the context of the security association (see clause B.11.3.3). Unless the profile version is incremented, PON-TAG is the same for System_Profile messages with all profile indices transmitted by the OLT CT. It is good practice to ensure that PON-TAG is unique within OLT CTs belonging to a common WRPSYS ID and fixed for the lifetime of the system. | +| 20-40 | Padding | Set to 0x00 by the transmitter; treated as "don't care" by the receiver. | +| 41-48 | MIC | Message integrity check, computed using the default PLOAM integrity key. | + +###### **B.7.3.3.8 Rate\_Control message** + +Table B.18 describes the Rate\_Control message. + +**Table B.18 – Rate\_Control message** + +| Octet | Content | Description | +|-------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1-2 | ONU-ID | Directed message to one ONU. | +| 3 | Message type ID | 0x1C, "Rate_Control". | +| 4 | SeqNo | Unicast PLOAM sequence number. | +| 5 | Operation code | 0x00: Request;
All parameters are applicable.
0x01: Complete_d.
Target downstream and upstream line rate parameters are applicable. Octets 6..8 are set to 0x00 by the OLT CT and ignored by the ONU. | +| 6-7 | Scheduled SFC | The 16 least significant bits of the superframe counter value of the PHY frame in the future when the ONU has to commence the transceiver tuning operation.
The specified value pertains to both downstream and upstream tuning. Whenever separate tuning is deemed beneficial, two unidirectional tuning actions executed serially can be considered. | +| 8 | Rollback flag | A bitmap of the form 0000 000R, where:
R – Rollback flag:
R=1: rollback available when tuning fails;
R=0: no rollback available when tuning fails. | + +**Table B.18 – Rate\_Control message** + +| Octet | Content | Description | +|-------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 9 | Nominal line rates | An octet of the form 0DDD 0UUU, where:
DDD – downstream nominal line rate:
DDD = 000: Rate class 1 (~10 Gbit/s)
DDD = 001: Rate class 2 (~25 Gbit/s)
DDD = 010: Rate class 3 (~50 Gbit/s)
DDD = 011: Rate class 4 (~100 Gbit/s)
UUU – upstream nominal line rate:
UUU = 000: Rate class 1 (~10 Gbit/s)
UUU = 001: Rate class 2 (~25 Gbit/s)
UUU = 010: Rate class 3 (~50 Gbit/s)
UUU = 011: Rate class 4 (~100 Gbit/s) | +| 10-40 | Padding | Set to 0x00 by the transmitter; treated as "don't care" by the receiver. | +| 41-48 | MIC | Message integrity check, computed using the default PLOAM integrity key. | + +##### **B.7.3.4 Upstream PLOAM message formats** + +###### **B.7.3.4.1 Serial\_Number\_ONU message** + +Information regarding Serial\_Number\_ONU message is provided in Table B.19. + +**Table B.19 – Serial\_Number\_ONU message** + +| Octet | Content | Description | +|-------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1-2 | ONU-ID | 0x00FF, Unassigned ONU-ID; or in case of an ONU with multiple PON interfaces undergoing activation on the second and subsequent PON interfaces, the ONU-ID previously assigned to the pilot PON interface, which has been activated first. | +| 3 | Message type ID | 0x01, "Serial_Number_ONU" | +| 4 | SeqNo | Set to 0x00 for all instances of Serial_Number_ONU PLOAM message. | +| 5-8 | Vendor_ID | See clause B.7.2.6.1. | +| 9-12 | VSSN | See clause B.7.2.6.2. | +| 13-16 | Reserved | Each octet set to 0x00 by the transmitter, treated as "don't care" by the receiver. | +| 17-18 | Correlation tag | See clause B.7.2.6.3. | +| 19-22 | Current downstream PON-ID | The PON-ID received by the ONU in its current downstream wavelength channel. | +| 23-26 | Current upstream PON-ID | The PON-ID of the Channel_Profile message containing the descriptor of the upstream wavelength channel in which the ONU is transmitting. | + +**Table B.19 – Serial\_Number\_ONU message** + +| Octet | Content | Description | +|----------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 27-34
(WRP) | SN Digest | A 64-bit value computed as a cryptographic hash over the publicly available serial number (SN) value and the shared secret Registration-ID:
Digest = AES-CMAC(Vendor_ID PON-ID VSSN PON-ID, Registration_ID 0x50746F50697353696D706C65, 64). | +| 35 | Reserved | Each octet set to 0x00 by the transmitter, treated as "don't care" by the receiver. | +| 36 | Reserved | Each octet set to 0x00 by the transmitter, treated as "don't care" by the receiver. | +| 37
(WRP) | Upstream line rate capability | A bitmap of the form 0000 ABCD indicating the ONU's upstream nominal line rate capability:
A – Rate class 1 (10 Gbit/s)
B – Rate class 2 (25 Gbit/s)
C – Rate class 3 (50 Gbit/s)
D – Rate class 4 (100 Gbit/s)
The bit value of 1 indicates that the respective rate class is supported; the bit value of 0 indicates the respective rate class is not supported. | +| 38 | Reserved | Each octet set to 0x00 by the transmitter, treated as "don't care" by the receiver. | +| 39 | Reserved | Each octet set to 0x00 by the transmitter, treated as "don't care" by the receiver. | +| 40 | Activation Debug Information | The octet of the form DDDD RRCS.
DDDD is the activation reason code that reflects the most recent transition to O2-3 state.
The Activation reason code has the following code points:
0000 – activation debug is not supported, no previous operation history is available, or the ONU is in a factory-fresh configuration.
0001 – Deactivate_ONU-ID PLOAM has been received in O2-3;
0010 – Not used for WDM PON;
0011 – Deactivate_ONU-ID PLOAM has been received in another state (that is, a state with a functional OMCC channel);
0100 – Calibration_Request PLOAM has been received in O2-3;
0101 – the ONU is being enabled after Emergency Stop (that is, after a sojourn in O7 state);
0110 – Loss of downstream synchronization (LODS) has occurred in O2-3;
0111 – Not used for WDM PON;
1000 – TOZ has expired in O2-3;
1001 – Not used for WDM PON;
1010 – TO2 has expired in O6;
1011 – TO4 has expired in O8;
1100 – TO5 has expired in O9;
1101 – ONU has lost power.
Other code points reserved. | + +**Table B.19 – Serial\_Number\_ONU message** + +| Octet | Content | Description | +|-------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | |
C is channel change flag, which is set in connection with a non-zero value of the Activation reason code to indicate that the wavelength channel has been changed, and the new value was pre-determined by the PLOAM protocol. The C flag is persistent between activation attempts, and is cleared, once the OMCC channel is established.
S is a scan flag which is set to indicate the current channel (which may or may not change from the previous activation) has been found in the course of wavelength channel scanning. The S flag is persistent between activation attempts, and is cleared, once the OMCC channel is established.
R – reserved; ONU sets this bit to zero.
| +| 41-48 | MIC | Message integrity check computed using the default PLOAM integrity key. | + +###### **B.7.3.4.2 Registration message** + +Information regarding Registration message is provided in Table B.20. + +**Table B.20 – Registration message** + +| Octet | Content | Description | +|-------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1-2 | ONU-ID | ONU-ID of the message sender. | +| 3 | Message type ID | 0x02, "Registration". | +| 4 | SeqNo | Repeated from downstream Request_Registration message. | +| 5-40 | Registration_ID | A string of 36 octets that has been assigned to the subscriber on the management level, entered into and stored in non-volatile storage at the ONU. Registration_ID may be useful in identifying a particular ONU installed at a particular location. The default is a string of 0x00 octets (Note). | +| 41-48 | MIC | Message integrity check computed using the default PLOAM integrity key. | + +NOTE – It is recommended that the Registration\_ID be a string of American standard code for information interchange (ASCII) characters, justified in the lower-numbered bytes of the registration message, and with 0x00 values in unused byte positions. + +###### **B.7.3.4.3 Acknowledgement message** + +Information regarding Acknowledgement message is provided in Table B.21. + +**Table B.21 – Acknowledgement message** + +| Octet | Content | Description | +|-------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | ONU-ID | ONU-ID of the message sender. | +| 3 | Message type ID | 0x09, "Acknowledgement". | +| 4 | SeqNo | Same as downstream sequence number. Set to the value of SeqNo in the downstream PLOAM message to which the present message provides an acknowledgement. | + +**Table B.21 – Acknowledgement message** + +| Octet | Content | Description | +|-------|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5 | Completion_code | Completion code:0x00: OK;
0x01: No message to send;
0x02: Busy, preparing a response;
0x03: Unknown message type;
0x04: Parameter error;
0x05: Processing error.
Other values reserved. | +| 6 | Attenuation | Attenuation parameter represents a requested attenuation level as a part of the power levelling instruction to an ONU, or an ONU's attenuation level at the time of the message transmission as a part of the power levelling report.
This is a one-octet field of the form 0000 MMMM, where MMMM is the attenuation level:
0000: Unattenuated transmission;
0001..0111: attenuation level in steps of 3dB. | +| 7 | Power levelling capability | Power levelling capability is a seven-bit bitmap of the form 0CCC CCCC, whereby a bit in the K-th least significant position indicates that the ONU supports the attenuation level of 3K dB. For example, 0000 0010 indicates support of 6dB attenuation level. | +| 8-40 | Padding | Set to 0x00 by the transmitter; treated as "don't care" by the receiver. | +| 41-48 | MIC | Message integrity check, computed using the ONU-specific derived shared PLOAM integrity key. | + +###### B.7.3.4.4 Rate\_Response message + +Information regarding Rate\_Response message is provided in Table B.22. + +**Table B.22 – Rate\_Response message** + +| Octet | Content | Description | +|-------|-----------------|----------------------------------------------------------------------------------------------------------------| +| 1-2 | ONU-ID | ONU-ID of the message sender | +| 3 | Message type ID | 0x1C, "Rate_Response". | +| 4 | SeqNo | Eight-bit unicast PLOAM sequence number. Repeats the value from the downstream Rate_Control PLOAM message. | +| 5 | Operation code | Operation code:
0x00: ACK;
0x01: NACK;
0x03: Complete_u;
0x04: ROLLBACK.
Other values reserved. | + +**Table B.22 – Rate\_Response message** + +| Octet | Content | Description | +|-------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6 | Response code | Response code:
0x00: As long as Operation code is ACK or Complete_u;
0x01: NACK due to downstream line rate being out of supported Rx tuning range;
0x02: NACK due to upstream line rate being out of supported Tx tuning range;
0x03: NACK due to ONU not being ready to start transceiver tuning by Scheduled SFC;
0x10: ROLLBACK due to no DSYNC on current downstream wavelength channel.
Other values reserved. | +| 7-40 | Padding | Set to 0x00 by the transmitter; treated as "don't care" by the receiver. | +| 41-48 | MIC | Message integrity check, computed using the default PLOAM integrity key. | + +### **B.8 WDM PON ONU activation cycle** + +#### **B.8.1 Causal sequence of activation events** + +The OLT CT controls the WDM PON ONU activation by means of exchanging upstream and downstream PLOAM messages. The outline of the activation events in their causal order is given below: + +- 1) The activating ONU tunes its receiver to search for the downstream wavelength channel, attains synchronization to user data and management TC data and collects the system, channel and profile information, confirming the channel partition, downstream and upstream channel frequency, line rate, downstream and upstream wavelength channel ID, service type, and channel assignment. The ONU may repeat the downstream wavelength channel search as necessary. +- 2) Once the ONU confirms the downstream wavelength channel, it makes best effort to tune its transmitter to specified upstream wavelength channel and starts announcing its presence on the PON with a Serial\_Number\_ONU PLOAM message, which also contains authenticating information. +- 3) When the OLT CT successfully authenticates the ONU, it provides a confirmation using the Assign\_ONU-ID PLOAM message. +- 4) The ONU completes activation and starts operation. + +#### **B.8.2 WDM PON ONU activation cycle state machine** + +##### **B.8.2.1 WDM PON ONU activation states, timers and inputs** + +Table B.23 summarizes the ONU activation cycle states. + +**Table B.23 – ONU activation cycle states** + +| ONU State/Substate | | Semantics | +|--------------------------------------------------------------------------------------------|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Ref | Full name | | +| O1 | Initial state | The ONU enters the Initial state (O1) when it originally powers up, or upon reactivation. The transmitter is off. | +| | O1/Off-Sync
≡ O1.1 | The substate is the entry point to O1 state.
The ONU searches for the downstream wavelength channel, attempting to achieve synchronization in both user data and management TC data paths. Once the downstream synchronization is attained, the ONU transitions to the O1/Profile Learning substate. | +| | O1/Profile Learning
≡ O1.2 | The ONU collects profile information from the management TC data path, determines whether the channel is available and verifies the PON-TAG digest. | +| O2-3 | Serial Number state | The ONU starts the discovery timer TOZ.
The ONU activates its transmitter.
The ONU transmits Serial_Number_ONU PLOAM message regularly, providing authenticating information, until the OLT CT confirms ONU-ID assignment. ONU returns to O1 state upon timer TOZ expiration | +| O5 | Operation state | The ONU enters the Operation state (O5) when it receives and transmits user data and management TC data. | +| | O5/Operating
≡ O5.1 | The substate is the entry point to O5 state.
The ONU receives and transmits user data and management TC data. | +| | O5/Management LODS
≡ O5.3 | The ONU enters this substate from the Operating (O5.1) following the loss of downstream synchronization in the management TC data path, or from the Intermittent LODS state (O6) following the restoring of downstream synchronization in the user data path.
Upon entry to the Management LODS state (O5.3), the ONU starts timer TOM and keeps the communication of user data. If the downstream synchronization is restored in management TC data path, before timer TOM expires, the ONU transitions back into the Operating (O5.1). Upon timer TOM expires or following the loss of downstream synchronization in the user data path, the ONU transitions to the Intermittent LODS state (O6). | +| O6 | Intermittent LODS state | The ONU enters this state from the Operation state (O5) following the loss of downstream synchronization in the user data path or TOM expires.
Upon entry to the Intermittent LODS state (O6), the ONU starts timer TOL. If the downstream synchronization is restored in the user data path, before timer TOL expires, the ONU transitions back into the Management LODS state (O5.3). Upon timer TOL expiration, the ONU transitions to the Initial state (O1). | +| O7 | Emergency Stop state | The ONU switches its transmitter off, but maintains downstream synchronization to both user data and management TC data paths, and parses the management TC data information. | +| * The substate O5.2 is specified in other PON system, but is irrelevant to WDM PON system. | | | + +Table B.24 summarizes the ONU activation cycle state machine timers. + +**Table B.24 – ONU activation cycle state machine timers** + +| Timer | Full name | State | Semantics and initial value | +|-------|--------------------------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TOZ | Discovery timer | O2-3 | Timer TOZ controls the duration of an ONU discovery attempt in the Serial Number state (O2-3), forcing a transition to the Initial state (O1) if the discovery feedback from the OLT CT is lacking. | +| TOM | Management synchronisation recovery timer | O5/Management LODS | Timer TOM is used to assert a failure to recover from a Management LODS condition by limiting the time an ONU can remain in the Management LODS (O5.3). | +| TOL | Loss of downstream synchronization (LODS) timer. | O6 | Timer TOL is used to assert a failure to recover from an intermittent LODS condition by limiting the time an ONU can remain in the Intermittent LODS state (O6). | + +The Applicable states column in Table B.25 includes all states where the event may occur in principle, including due to protocol error. Whether an event requires processing is indicated in Table B.26. + +**Table B.25 – ONU activation cycle state machine inputs** + +| Input | Applicable states | Semantics | +|------------------------------------------|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Downstream synchronization events | | | +| DSYNC | O1/Off-Sync; O6; | Downstream synchronization attained. The event is generated when the synchronization has been achieved in the downstream user data path. | +| LODS | All states and substates, except O1/Off-Sync; O6; | Loss of downstream synchronization. The event is generated when the downstream synchronization in the user data path is lost. | +| MDSYNC | O1/Off-Sync; O5/Management LODS | Management downstream synchronization attained. The event is generated when the synchronization has been achieved in the downstream management TC data path. | +| MLODS | O1/Profile Learning; O2-3; O5/Operating | Management loss of downstream synchronization. The event is generated when the downstream synchronization in the management TC data path is lost. | +| Internal events | | | +| DWLCH ok to work | O1/Profile Learning; | The channel is available and the PON-TAG digest is successfully verified. | +| DWLCH not appropriate | O1/Profile Learning; | The channel is engaged, or the PON-TAG digest verification is unsuccessful. | +| Timer events | | | +| TOZ expires | O2-3 | Timer expiration | +| TOM expires | O5/Management LODS | Timer expiration | +| TOL expires | O6 | Timer expiration | +| PLOAM events | | | +| ONU-ID Assignment | O1/Profile Learning, O2-3, O5, O7 | Assign_ONU-ID PLOAM message with matching SN received. | +| Deactivate ONU-ID request | O1/Profile Learning, O2-3, O5, O7 | Deactivate_ONU-ID PLOAM message received | +| Disable SN request | O1/Profile Learning, O2-3, O5, O7 | Disable_Serial_Number PLOAM message with Disable option received | +| Enable SN request | O1/Profile Learning, O2-3, O5, O7 | Disable_Serial_Number PLOAM message with Enable option received. | + +**Table B.25 – ONU activation cycle state machine inputs** + +| Input | Applicable states | Semantics | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------------------------------------| +| Other PLOAM messages* | | | +| System_Profile | O1/Profile Learning, O2-3, O5, O7 | PLOAM message of specific type is received. | +| Channel_Profile | same as above | PLOAM message of specific type is received. | +| Key_control | same as above | PLOAM message of specific type is received. | +| Rate_Control | same as above | PLOAM message of specific type is received. | +| * Although the input events of this part do not drive the ONU state machine, their effect depends on the ONU state at the time the event occurs (the message is received). | | | + +**B.8.2.2 ONU state diagram** + +The WDM PON ONU activation cycle state transition diagram is graphically represented in Figure B.8. + + + +Detailed description of Figure B.8: The diagram shows the state machine for ONU activation. + 1. **Initial state (O1)**: A large box containing two sub-states: **Off-Sync (O1.1)** and **Profile Learning (O1.2)**. Transitions between them are 'DSYNC and MDSYNC' (O1.1 to O1.2) and 'LODS, MLODS, or DWLCH not appropriate' (O1.2 to O1.1). + 2. **Serial Number state (O2-3)**: Transition from O1.2 to O2-3 is triggered by 'DWLCH OK to work'. + 3. **Operation state (O5)**: A large box containing **Operating (O5.1)** and **Management LODS (O5.3)**. Transition from O2-3 to O5.1 is 'ONU-ID assignment'. Transitions within O5: 'MLODS' (O5.1 to O5.3) and 'MDSYNC' (O5.3 to O5.1). + 4. **Intermittent LODS state (O6)**: Transitions from O5.1/O5.3 to O6 are triggered by 'LODS' or 'LODS, or TOM expires'. Transition from O6 back to O5.3 is 'DSYNC'. + 5. **Emergency Stop state (O7)**: Transitions to O7 come from O1, O2-3, and O5 via 'Disable SN request'. Transition from O7 back to O1 is 'Enable SN request'. + 6. **Global transitions to O1.1**: From O2-3 ('LODS, MLODS, TOZ expires, or deactivate ONU-ID request'), from O5 ('Deactivate ONU-ID request'), and from O6 ('TOL expires'). + +Figure B.8 – WDM PON ONU state diagram + +**Figure B.8 – WDM PON ONU state diagram** + +**B.8.2.3 ONU state transition table** + +In Table B.26 a shaded cell indicates that an event is not applicable in the given state; a dash within a cell indicates that the event is not processed (ignored) in the given state. For the receipt of the PLOAM messages that do not drive the ONU activation cycle state machine, Table B.26 only indicates whether the event is processed (plus) or ignored (dash) in the given state. The specific effects + +Rec. ITU-T G.9802.2 (07/2023) 59 + +of the PLOAM message receipt are discussed in the corresponding clauses of this Recommendation. The TC layer configuration parameter sets referenced in Table B.26 are specified in Table B.27. + +**Table B.26 – WDM PON ONU activation cycle state transition table** + +| Events | ONU activation cycle states | | | | | | | +|----------------------------------------------------------------------|----------------------------------|-----------------------|--------------------------------|----------------------|--------------------------------|------------------------|-------------------------| +| | Initial state O1 | | Serial Number state O2-3 | Operations state O5 | | Intermittent LODS O6 | Emergency Stop state O7 | +| | Off-Sync O1.1 | Profile Learning O1.2 | | Operating O5.1 | Management LODS O5.3 | | | +| Power up
If last operational state was O7 ==> O7
else ==> O1.1 | | | | | | | | +| Downstream synchronization attained DSYNC | Both DSYNC and MDSYNC; ==> O1.2; | | | | | Stop TOL; ==> O5.3; | | +| Loss of downstream synchronization LODS | | Discard I; ==> O1.1; | Discard I; Stop TOZ; ==> O1.1; | Start TOL; ==> O6; | Start TOL; Stop TOM; ==> O6; | | – | +| Downstream management synchronization attained MDSYNC | Both DSYNC and MDSYNC; ==> O1.2; | | | | Stop TOM; ==> O5.1; | | | +| Loss of downstream management synchronization MLODS | | Discard I; ==> O1.1; | Discard I; Stop TOZ; ==> O1.1; | Start TOM; ==> O5.3; | | | | +| Downstream wavelength channel is OK to work | | Start TOZ; ==> O2-3 | | | | | | +| Downstream wavelength channel is not appropriate | | Discard I; ==> O1.1; | | | | | | +| Timer TOZ expires | | | Discard I; ==> O1.1; | | | | | +| Timer TOL expires | | | | | | {Discard V; ==> O1.1;} | | +| Timer TOM expires | | | | | ==> O6; | | | +| ONU-ID assignment | | – | Set II; Stop TOZ; ==> O5; | | | | – | +| Directed deactivate ONU-ID request | | – | – | Discard V; ==> O1.1; | Discard V; Stop TOM; ==> O1.1; | | – | +| Disable SN request | | ==> O7; | Stop TOZ; ==> O7; | ==> O7; | Stop TOM; ==> O7; | | – | +| Enable SN request | | – | – | – | – | | Discard VI; ==> O1.1 | +| System_Profile | | + | + | | | | – | +| Channel_Profile | | + | + | | | | – | +| Key_Control | | – | – | | | | – | +| Protection_Control (FFS) | | – | – | + | | | – | +| Rate_control | | – | – | + | + | | – | + +The composition of the TC layer configuration parameter sets referenced in Table B.26 is specified in Table B.27. + +**Table B.27 – Reference TC layer configuration parameter sets** + +| TC layer configuration item | Parameter set | | | | | | | +|-----------------------------|---------------|----|-----|----|---|----|-----| +| | I | II | III | IV | V | VI | VII | +| System profile parameters | | | | | | X | X | +| Channel profile parameters | | | | | | X | X | +| ONU-ID | | X | X | | X | X | | +| Default XGEM Port-ID | | X | X | | X | X | | + +### B.9 OLT and ONU timing relationships + +This clause is for further study. + +### B.10 Performance monitoring, supervision and defects + +This clause focuses on mechanisms to detect link failure and monitor the health and performance of the links. It does not cover functions that may utilize the performance monitoring information, such as station management or provisioning. + +#### B.10.1 Performance monitoring + +To facilitate troubleshooting, it is desirable that OLT channel termination and ONU maintain a variety of performance monitoring (PM) counters. The collected counter values may trigger actions ranging from threshold crossing alerts to alarms to protection switching, which are largely beyond the scope of this Recommendation. + +This clause identifies mandatory and optional PM parameters, and for the PM parameters collected at the OLT CT. + +Monitoring of optical parameters, for example, transmitted and received optical power, is specified in [ITU-T G.988]. + +Counters collected at the ONU are available to the OLT CT using OMCI. + +Table B.28 summarizes performance monitoring parameters. + +**Table B.28 – Performance monitoring parameters** + +| Parameter | Mandatory or optional | Description | Collected by: | | Notes | +|-------------------------|-----------------------|--------------------------------------------------------------------------------------|------------------------------------|---------------------------------|-------| +| | | | Each ONU | OLT CT | | +| PHY PM | | | | | | +| Corrected FEC bytes | M | The number of bytes that were corrected by the FEC function. | Yes, if downstream FEC is enabled. | Yes, if upstream FEC is enabled | | +| Corrected FEC codewords | M | Count of FEC codewords that contained errors but were corrected by the FEC function. | Yes, if downstream FEC is enabled. | Yes, if upstream FEC is enabled | | + +**Table B.28 – Performance monitoring parameters** + +| Parameter | Mandatory or optional | Description | Collected by: | | Notes | +|--------------------------------------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|---------------------------------|-----------------| +| | | | Each ONU | OLT CT | | +| Uncorrectable FEC codewords | M | Count of FEC codewords that contained errors and could not be corrected by the FEC function. | Yes, if downstream FEC is enabled. | Yes, if upstream FEC is enabled | | +| Total FEC codewords | M | Count of total received FEC codewords. | Yes, if downstream FEC is enabled. | Yes, if upstream FEC is enabled | | +| Total received words protected by BIP-32 | M | Count of received 4-byte words that are included in BIP-32 check. | Yes | Yes | | +| BIP-32 error count | M | Count of bit errors according to BIP-32 (Note). | Yes | Yes | | +| PSB HEC error count | O | HEC error in any of the fields of PSB | Yes | Yes | | +| FS HEC error count | O | FS header HEC errors received. | Yes | Yes | | +| LODS PM | | | | | | +| Total number of LODS events | M | Counter of state transitions from O5.1/O5.3 to O6 | Yes | N/A | ONU local event | +| XGEM PM | | | | | | +| Transmitted XGEM frames | M | Total number of XGEM frames transmitted. | Yes | Yes | | +| Received XGEM frames | M | Total number of XGEM frames received. | Yes | Yes | | +| Count of the number of transmitted XGEM frames with LF bit NOT set | O | Number of transmit fragmentation operations. | Yes | Yes | | +| Count of XGEM frame header HEC errors | M | Number of events involving loss of XGEM channel delineation. | Yes | Yes | | +| Count of FS frame words lost due to XGEM frame HEC error. | O | Aggregate severity measure of the loss of XGEM channel delineation events. Note that the number of lost XGEM frames is not available. | Yes | Yes | | +| UTILIZATION PM | | | | | | +| Transmitted bytes in non-idle XGEM frames | M | Measure of downstream utilization | Yes | Yes | | +| Received bytes in non-idle XGEM frames | M | Measure of upstream utilization | Yes | Yes | | + +**Table B.28 – Performance monitoring parameters** + +| Parameter | Mandatory or optional | Description | Collected by: | | Notes | +|-------------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------|---------------|------------------|-------| +| | | | Each ONU | OLT CT | | +| PLOAM PM | | | | | | +| PLOAM MIC errors | O | Counter of received PLOAM messages with MIC errors | Yes | Yes | | +| PLOAM timeouts | O | Retransmission count: missing, late or errored response.
No response to Request_Registration, lack of ACK, etc. | N/A | Yes | | +| Downstream PLOAM message count | O | Count of PLOAM messages sent by OLT CT, received by ONU, either unassigned or directed to the specific ONU-ID. | Yes | Yes (unassigned) | | +| System_Profile message count | O | Count of PLOAM messages sent by OLT CT | Yes | Yes | | +| Channel_Profile message count | O | Count of PLOAM messages sent by OLT CT | Yes | Yes | | +| Assign_ONU-ID message count | O | Count of PLOAM messages sent by OLT CT | Yes | Yes | | +| Deactivate_ONU-ID message count | O | Count of PLOAM messages sent by OLT CT | Yes | Yes | | +| Disable_Serial_Number message count | O | Count of PLOAM messages sent by OLT CT | Yes | Yes | | +| Request_Registration message count | O | Count of PLOAM messages sent by OLT CT | Yes | Yes | | +| Rate_Control message count | O | Count of PLOAM messages sent by OLT CT | Yes | Yes | | +| Upstream PLOAM message count | O | Count of messages (other than Acknowledgement) sent by ONU, received by OLT CT. | Yes | Yes | | +| Serial_Number_ONU message count | O | Count of PLOAM messages sent by ONU | Yes | Yes | | +| Registration message count | O | Count of PLOAM messages sent by ONU | Yes | Yes | | +| Acknowledgement message count | O | Count of PLOAM messages sent by ONU | Yes | Yes | | +| Sleep_Request message count | O | Count of PLOAM messages sent by ONU | Yes | Yes | | +| Rate_Response message count, | O | Count of PLOAM messages sent by ONU | Yes | Yes | | +| Activation PM | | | | | | +| OMCI PM | | | | | | + +**Table B.28 – Performance monitoring parameters** + +| Parameter | Mandatory or optional | Description | Collected by: | | Notes | +|---------------------------------------------------------------------|-----------------------|---------------------------------------------------------------------|---------------|--------|-------| +| | | | Each ONU | OLT CT | | +| OMCI baseline message count | O | OMCI message count | Yes | Yes | | +| OMCI extended message count | O | OMCI message count | Yes | Yes | | +| OMCI MIC errors | O | Count of received OMCI messages with MIC errors | Yes | Yes | | +| Energy conservation | | | | | | +| Time spent in each of the OLT CT/ONU low-power states, respectively | O | Time spent in each of the OLT CT/ONU low-power states, respectively | Yes | Yes | | + +NOTE – The BIP-32 error count is used to obtain a BER estimate only when FEC is off. + +#### B.10.2 Defects + +This clause captures the required actions that are performed in the TC layer, as opposed to those left to the discretion of an implementer. In particular, the effects of repeated defects of the same type are an implementation matter. + +##### B.10.2.1 Items detected at OLT channel termination + +Table B.29 summarizes defects detected at the OLT CT. + +**Table B.29 – Defects detected at the OLT CT** + +| Type | Description | | | | | +|------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|---------| +| | | Detection conditions | Actions | Cancellation conditions | Actions | +| LOS | Loss of signal | The OLT CT did not receive any expected transmissions in the upstream (complete PON failure) for four consecutive frames. | At the discretion of the OLT CT; may require additional diagnostic to determine whether PON has been lost, and ultimately lead to protection switching event. | When the OLT CT receives upstream transmission. | – | +| SUFi | Start-up failure of ONU i . | The OLT CT detects the ONU's serial number, but the ONU fails to complete the bring-up sequence. | Send Deactivate_ONU-ID PLOAM message. | The ONU is ranged successfully. | | + +**Table B.29 – Defects detected at the OLT CT** + +| Type | | Description | | | | +|-------|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|---------| +| | | Detection conditions | Actions | Cancellation conditions | Actions | +| DFi | Disable failure of ONU. | The ONU responds to an attempt to disable the ONU using its serial number (with one or more Disable_Serial_Number PLOAM messages) which may have been preceded by a failed attempt to deactivate the ONU (with one or more Deactivate_ONU PLOAM messages).
Note that the OLT CT can detect this condition only if it continues to provide upstream bandwidth allocations to the ONU. | Mitigating action at OLT CT discretion. May include rogue ONU diagnostic procedures. The offending ONU-ID and the associated Alloc-IDs may have to be blocked from re-allocation. | The offending ONU is successfully re-activated and remains positively controlled, or is prevented from transmitting upstream. | | +| LOPCi | Loss of PLOAM channel with ONU i . | Generic defect indicating breakage of the PLOAM protocol: persistent MIC failure in the upstream; lack of acknowledgements or proper PLOAM responses from the ONU. Persistent means that the same irregular condition is observed consecutively at least three times. | Mitigating action at the OLT CT discretion; may include ONU re-authentication, ONU deactivation or disabling, or execution of rogue ONU diagnostic procedures. | | – | + +##### B.10.2.2 Items detected at ONU + +Table B.30 summarizes defects detected at the ONU. + +**Table B.30 – Defects detected at the ONU** + +| Type | | Description | | | | +|------|-------------------------------------|------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|---------------------------------------------------------------------| +| | | Detection conditions | Actions | Cancellation conditions | Actions | +| LODS | Loss of downstream synchronization. | The ONU downstream synchronization state machine in the Hunt or Pre-Sync states. (See clause B.8.2.) | Provide necessary visual indication and user-side interface signalling. Execute appropriate transition of the ONU activation state machine. | The ONU downstream synchronization state machine in the Sync or Re-Sync states. | Execute appropriate transition of the ONU activation state machine. | + +##### B.10.2.3 Urgent ONU status snapshot record + +To facilitate post-mortem diagnostics, the ONU supports recording a snapshot of relevant ONU status information, defects and failure conditions. The information is collected and stored by the ONU when communication channel with the OLT CT is compromised or unavailable. + +The urgent status snapshot record is made as a part of the dying gasp (DG) sequence, and any time the transmitter is being switched off by the ONU software. It can be retrieved either remotely on site or in the lab upon ONU replacement. The urgent status snapshot record is stored in non-volatile memory to ensure it survives ONU reactivation, warm and cold reboot, power cycle, and power loss. The storage is expected to accommodate at least ten urgent status snapshot records and to be reasonably protected against accidental erasure and unauthorized access. + +### **B.11 WRP Security** + +This clause discusses threat model characteristics for the WRP operating environment, and specifies authentication, data integrity and privacy protection aspects of the system. + +#### **B.11.1 Threat model for WRP** + +WRP security is intended to protect against the following threats: + +- 1) An attacker could connect a malicious device at various points on the infrastructure (e.g., by tampering with street cabinets, spare ports or fibre cables). Such a device could intercept and/or generate traffic. Depending on the location of such a device, it could impersonate an OLT CT or alternatively it could impersonate an ONU. +- 2) A malicious user in first scenario could record packets transmitted on the passive optical network (PON) and replay them back onto the PON later, or conduct bit-flipping attacks. + +Passive optical networks (PONs) are deployed in a wide variety of scenarios. In some cases, the ODN, the optical splitter, or even the ONUs may be installed in a manner considered to be physically secure or tamper-proof. + +To accommodate these scenarios in an economical manner, activation of some of the WRP security features is optional, as indicated in the clauses below. + +#### **B.11.2 Authentication** + +The WRP system supports three mechanisms for authentication. The first mechanism is based on the use of Registration\_ID. It is executed in the course of ONU activation and may be repeated throughout the duration of the activation cycle, i.e., until the ONU's next entry into the Initial state (O1). The registration-based authentication mechanism provides a basic level of authentication of the ONU to the OLT CT. It does not provide authentication of the OLT CT to the ONU. Support of the registration-based authentication mechanism is mandatory in all WRP devices. The two other authentication mechanism provide secure mutual authentication to both OLT CT and ONU. One of them is based on an ONU management and control interface (OMCI) message exchange (see Annex C). The other is based on an IEEE 802.1X message exchange and provides a wide range of extensible features (see Annex D). Support for OMCI-based and IEEE 802.1X-based authentication mechanism is mandatory for implementation at the component level, but optional from an equipment specification perspective. In other words, the transmission convergence (TC) layer implementation will have the capability to support both secure mutual authentication methods, but equipment constructed using these TC-layer implementation may choose not to support them. + +It is within the discretion of an operator to require support of one or both secure mutual authentication mechanisms at the equipment specification stage, and to employ any or none of the authentication methods, including the basic registration-based authentication, when the system is in service. + +Upon authentication failure, the OLT CT may undertake measures to restore functionality and to prevent a potential security breach, which may include repeating authentication using the same or an alternative mechanism, blocking upstream and downstream traffic, deactivating or disabling the offending ONU, or executing the rogue ONU diagnostic procedures. + +##### **B.11.2.1 Registration-based authentication** + +The registration-based authentication mechanism can provide authentication of ONU to OLT CT, but not vice versa. Its support is mandatory for all WRP systems. To maintain full functionality, this method requires: + +- that a Registration\_ID be assigned to a subscriber at the management level; +- that the Registration\_ID be provisioned into the OLT CT and be communicated to the field personnel or to the subscriber directly; +- that the ONU support a method for entering the Registration\_ID in the field (specification of such a method being beyond the scope of this Recommendation); +- that the field personnel or the subscriber in fact enter the Registration\_ID into the ONU. + +The Registration\_ID is stored at the ONU in a non-volatile storage. It is retained through ONU re-activation and power cycle, until explicitly reset by the field personnel or the subscriber. + +###### **B.11.2.1.1 The OLT CT perspective** + +The OLT CT must support ONU authentication based on the reported Registration\_ID, as well as the MSK and derived shared key calculation procedure based on the reported Registration\_ID (see clause B.11.3). + +The OLT CT requests the Registration\_ID from the ONU in the following situations: + +- As a final handshake upon completion of a secure mutual authentication procedure, by sending a Request\_Registration message to the ONU. +- At any time throughout the ONU's activation cycle at its own discretion, by sending a Request\_Registration message to the ONU. + +If at the time of Registration\_ID receipt from the ONU, there is no valid secure mutual association (SMA) between the OLT CT and the ONU (i.e., in the course if secure mutual authentication has not been executed or has failed), the OLT CT: + +- must compute the master session key (MSK) and derived shared keys based on the reported Registration\_ID; +- may perform authentication of the ONU based on the reported Registration\_ID. + +It is up to the operator to specify whether registration-based authentication is performed and how the result is used. Failure of registration-based authentication shall not prevent the OLT CT from maintaining management level communication with the ONU, but may have an effect on how the OLT CT further handles the ONU and, in particular, on subsequent provisioning of services. + +Registration-based authentication is not performed and the registration-based MSK and derived shared keys are not calculated, if at the time of the Registration\_ID report there exists a valid SMA between the OLT CT and the ONU. + +Once the OLT CT transmits a Request\_Registration message to the ONU while expecting to use the reported Registration\_ID for shared key derivation, it refrains from sending to that ONU other PLOAM or OMCI messages with ONU-specific MIC (see clauses B.11.3.2 and B.11.3.3) until after the Registration\_ID is received and the registration-based MSK and derived shared keys are calculated. + +Once the OLT CT completes calculation of the registration-based MSK and derived shared keys for a particular ONU, it immediately commits those keys as active. + +At the start of the ONU's activation cycle, the OLT CT discards any active registration-based MSK and derived shared keys. + +###### **B.11.2.1.2 The ONU perspective** + +The ONU must be able to perform calculation of the MSK and derived share keys based on the `Registration_ID`. + +The ONU computes the registration-based MSK and derived shared keys upon power up (initially, using the well-known default `Registration_ID` (see clause B.7.3.4.2), and each time the `Registration_ID` changes. The computed values are stored for future use. As the registration-based key set may be required at any time, the ONU may benefit by storing the registration-based MSK and derived shared keys separately from the MSK and derived shared keys based on secure mutual authentication. + +ONU reports `Registration_ID` to the OLT in the following situations: + +- At any time during the ONU's activation cycle, in response to a `Request_Registration` message. + +The events that cause registration-based key re-computation are asynchronous to the physical layer operations, administration and maintenance (PLOAM) channel events. The ONU is expected to have the registration-based MSK and derived shared keys available at the time it reports its `Registration_ID` to the OLT CT. + +If there is no valid SMA between the OLT CT and the ONU, the ONU commits the set of shared keys based on the reported `Registration_ID` immediately upon sending the `Registration` PLOAM message. + +The ONU retains the `Registration_ID` and the stored registration-based MSK and derived shared keys between activation cycles and between power cycles. + +##### **B.11.2.2 Secure mutual authentication options** + +Two secure mutual authentication mechanisms are defined: OMCI-based authentication (Annex C), and IEEE 802.1X-based authentication (Annex D). These mechanisms authenticate the OLT CT to the ONU as well as the ONU to the OLT CT. The support of both secure mutual authentication mechanisms is optional on the system level. + +If secure mutual authentication is supported by the system and is employed by the operator, the OLT CT initiates the secure mutual authentication procedure using an appropriate mechanism upon completion of the ONU activation procedure before user data traffic is transmitted, and subsequently may initiate re-authentication at any time, subject to the operator's policies and discretion. + +In the course of execution of a secure mutual authentication procedure, the OLT CT and the ONU compute the secure master session key (MSK) and a set of secure shared keys applicable for specific management and operation tasks. + +Both the OLT CT and the ONU discard the MSK and derived shared keys obtained in the course of secure mutual authentication at the start of the ONU's activation cycle along with the other TC layer parameters. + +#### **B.11.3 Key derivation** + +The mathematical details of the MSK and derived shared key calculation are shared by the OLT CT and the ONU. + +The ONU computes the registration-based MSK and derived shared keys upon power up (initially using the well-known default `Registration_ID` (see clause B.7.3.4.2), and each time the `Registration_ID` changes. + +The OLT CT computes the registration-based MSK and derived shared keys each time when the ONU reports its `Registration_ID` to the OLT CT in response to the `Request_Registration` PLOAM message, but only when there is no valid mutual security association between OLT CT and ONU. + +Both the OLT CT and the ONU compute the secure MSK and derived shared keys each time a secure mutual authentication procedure using either the OMCI-based or the IEEE 802.1X-based mechanism is executed. + +##### B.11.3.1 Cryptographic method + +The secure key derivation procedure employs the cipher-based message authentication code (CMAC) algorithm specified in [b-NIST SP800-38B] with the advanced encryption standard (AES) encryption algorithm [b-NIST FIPS-197] as the underlying block cipher. + +The AES-CMAC function takes as its inputs: + +- block cipher key $K$ ; +- the information message $M$ ; and +- the bit length of the output $Tlen$ , + +and produces the message authentication code $T$ of length $Tlen$ as an output. The notation for invocation of the AES-CMAC function is: + +$$T = \text{AES-CMAC}(K, M, Tlen) \quad (\text{B-1})$$ + +For the purposes of this Recommendation, the block size of the underlying block cipher and the bit length of the AES key are 128 bits. This version of the block cipher is referred to herein as AES-128. + +##### B.11.3.2 Master session key + +The master session key (MSK) is a 128-bit value that is shared between the OLT CT and the given ONU as a result of an authentication procedure, and which serves as a starting point for the derivation of all of the other secret keys used in subsequent secure communications. + +For the registration-based key derivation, the MSK is obtained from the ONU Registration\_ID: + +$$\text{MSK} = \text{AES-CMAC}((0x55)_{16}, \text{Registration\_ID}, 128) \quad (\text{B-2})$$ + +Here $(0x55)_{16}$ denotes a default key composed of the hex pattern 0x55 repeated 16 times, and Registration\_ID is the 36-byte value transmitted in the Registration PLOAM message. Note that the Registration PLOAM message may carry either an ONU-specific Registration\_ID, or a well-known default value. + +When the key derivation is triggered by the success of secure mutual authentication, the procedure to obtain the MSK depends on the specific authentication mechanism. + +##### B.11.3.3 Derived shared keys + +The session key (SK) binds the MSK to the context of the security association between the OLT CT and ONU. The SK, which is used for subsequent key derivations, is obtained using the following formula: + +$$\text{SK} = \text{AES-CMAC}(\text{MSK}, (\text{SN} \mid \text{PON-TAG} \mid 0x53657373696f6e4b), 128) \quad (\text{B-3})$$ + +where the information message, which is 24 bytes long, is a concatenation of three elements: the ONU serial number (SN) as reported in octets five to 12 of the upstream Serial\_Number\_ONU PLOAM message (clause B.7.3.4.1), the PON-TAG as reported in octets 12 to 19 of the downstream System\_Profile PLOAM message (clause B.7.3.3.7), and the hexadecimal representation of the ASCII string "SessionK". + +The OMCI integrity key (OMCI\_IK) is used to generate and verify the integrity of OMCI messages. The OMCI\_IK is derived from the SK by the following formula: + +$$\text{OMCI\_IK} = \text{AES-CMAC}(\text{SK}, 0x4f4d4349496e746567726974794b6579, 128) \quad (\text{B-4})$$ + +Here the information message parameter of the AES-CMAC function is 128 bits long, and is the hexadecimal representation of the ASCII string "OMCIIntegrityKey". + +The PLOAM integrity key (PLOAM\_IK) is used to generate and verify the integrity of FS layer unicast PLOAM messages. The PLOAM\_IK is derived from the SK by the following formula: + +$$\text{PLOAM\_IK} = \text{AES-CMAC} (\text{SK}, 0\text{x}504\text{c}4\text{f}414\text{d}496\text{e}7465677274794\text{b}6579, 128) \quad (\text{B-5})$$ + +Here the information message parameter of the AES-CMAC function is 128 bits long, and is the hexadecimal representation of the ASCII string "PLOAMIntegrityKey". + +For downstream unassigned ONU-ID PLOAM messages and for unicast PLOAM messages exchanged in the course of ONU activation prior to availability of the registration-based MSK, the default PLOAM\_IK value is used, which is equal to $(0\text{x}55)_{16}$ , the subscript indicating the multiplicity of repetition of the specified hex pattern. + +#### B.11.4 Integrity protection and data origin verification for PLOAM + +For the PLOAM messaging channel, sender identity verification and protection against forgery is achieved with the use of the 8-byte message integrity check (MIC) field of the PLOAM message format. + +##### B.11.4.1 Cryptographic method + +The MIC field of the PLOAM message format is constructed using the cipher-based message authentication code (CMAC) algorithm specified in [b-NIST SP800-38B] with the 128-bit Advanced encryption standard (AES-128) encryption algorithm [b-NIST FIPS-197] as the underlying block cipher (see Figure B.9). + +The parameters and the notation for invocation of the AES-CMAC function are described in clause B.11.3.1. + +##### B.11.4.2 MIC calculation + +Given the 40 bytes of the PLOAM message content and the PLOAM integrity key PLOAM\_IK, the sender and the receiver can calculate the MIC field as follows: + +$$\text{PLOAM-MIC} = \text{AES-CMAC} (\text{PLOAM\_IK}, C_{\text{dir}} \mid \text{PLOAM\_CONTENT}, 64) \quad (\text{B-6})$$ + +Where $C_{\text{dir}}$ is the direction code: $C_{\text{dir}} = 0\text{x}01$ for downstream and $C_{\text{dir}} = 0\text{x}02$ for upstream, and *PLOAM\_CONTENT* denotes octets 1 to 40 of the PLOAM message. + + + +| | | +|--------|-----------------| +| 1..2 | ONU-ID | +| 3 | Message type ID | +| 4 | SeqNo | +| 5..40 | Message_Content | +| 41..48 | MIC | + +Diagram illustrating the PLOAM integrity protection process. On the left, a 'PLOAM message' table shows fields: 1..2 ONU-ID, 3 Message type ID, 4 SeqNo, 5..40 Message\_Content, and 41..48 MIC. An arrow points from the first four fields to a 'Message' block containing 'Direction code', 'ONU-ID', 'Message type ID', 'SeqNo', and 'Message\_Content'. This 'Message' block (41 bytes) and a 'PLOAM\_IK' (16 bytes) are inputs to an 'AES-CMAC-64 engine'. The engine outputs an 8-byte MIC, which is then placed into the 41..48 field of the PLOAM message. The diagram is labeled G.9802.2(23). + +Figure B.9 – PLOAM integrity protection + +#### B.11.5 Integrity and data origin verification key switching + +##### B.11.5.1 Use of the default key + +At the start of ONU activation, the PLOAM integrity key for the given ONU is set to the default value of $(0\text{x}55)_{16}$ , which is used for PLOAM message exchange while no MSK is available. Once the ONU communicates its Registration\_ID to the OLT CT, the basic MSK is established and all the derivative shared keys are obtained. The OMCI integrity key does not require an explicit default, as no OMCI exchange takes place prior to MSK establishment. + +The certain types of the upstream and downstream unicast PLOAM messages (such as the Serial\_Number\_ONU PLOAM message, the Deactivate\_ONU-ID PLOAM message, the Request\_Registration and Registration PLOAM messages) are always protected by a MIC that is generated with the default PLOAM integrity key. These messages, therefore, can be successfully transmitted even if the OLT CT and ONU have not established or no longer agree on the dynamically derived keys. See PLOAM message formats for individual PLOAM message types in clauses B.7.3.3 and B.7.3.4 for the details of the default PLOAM integrity key applicability. + +##### B.11.5.2 Key switching for OMCI-based secure mutual authentication + +The following description refers to the Enhanced security control attributes and procedures specified in clause 9.13.11 of [ITU-T G.988]. + +The authentication is implemented as a three-step symmetric-key-based challenge-response procedure in the OMCC channel followed by a PLOAM handshake in the form of Registration\_ID exchange. + +The OLT CT initiates the OMCI-based authentication at its discretion by writing the OLT CT random challenge table attribute. From this point to the completion of the authentication procedure, the OLT CT refrains from sending to the ONU any OMCI messages unrelated to authentication. + +The ONU generates a random challenge of its own, computes the response to the OLT CT challenge, and initiates the secure MSK and derived shared key calculation procedure. Once computed, the secure keys are stored for future use. + + + +The diagram illustrates the sequence of messages for OMCI-based secure mutual authentication between an OLT and an ONU. The vertical axis represents time, and horizontal arrows represent message exchanges. The legend indicates that white boxes represent 'Old key' and grey boxes represent 'New key'. + +**Sequence of Messages:** + +- The OLT sends a **Set\* [OLT crypto capabilities, OLT random challenge table]** message to the ONU. +- The OLT sends a **Set [OLT challenge status = true]** message to the ONU. +- The ONU responds with **AVC [ONU random challenge table complete]** to the OLT. +- The ONU sends **AVC [ONU authentication result table complete]** to the OLT. +- The OLT sends a **Get [ONU selected crypto capabilities, ONU random challenge table, ONU authentication result table]** message to the ONU. +- The ONU responds with **Get\_response []** to the OLT. +- The OLT sends a **Set\* [OLT authentication result table]** message to the ONU. +- The OLT sends a **Set [OLT result status = true]** message to the ONU. +- The ONU sends **AVC [ONU authentication status]** to the OLT. +- The OLT sends a **Get [Master session key name]** message to the ONU. +- The ONU responds with **Get\_response []** to the OLT. +- The OLT sends a **PLOAM: Request\_Registration** message to the ONU. +- The ONU responds with a **PLOAM: Registration** message to the OLT. + +**Key Switching:** + +- At the OLT, the **AVC [ONU authentication result table complete]** message triggers a switch from the old key to the new key for the PLOAM channel. +- At the ONU, the **AVC [ONU authentication status]** message triggers a switch from the old key to the new key for the OMCI channel. +- Both the OLT and ONU switch to the new key for the PLOAM channel upon receipt of the **PLOAM: Registration** message. + +**Legend:** + +- Old key +- New key + +G.9802.2(23) + +Sequence diagram of OMCI-based secure mutual authentication procedure between OLT and ONU. The diagram shows message exchanges over OMCC and PLOAM channels, with key switching from old to new keys. + +NOTE 1 – Set\* indicates multiple set operations as needed to fill the table. + +NOTE 2 – Unless explicitly specified otherwise, the messages are exchanged over the OMCC channel. + +**Figure B.10 – OMCI-based secure mutual authentication procedure** + +Upon receipt of the ONU's response to OLT CT's random challenge along with the ONU random challenge table (see Figure B.10), the OLT CT unilaterally verifies the ONU's authentication status. If the unidirectional ONU-to-OLT authentication fails, further execution of the authentication procedure is aborted. If the unidirectional ONU-to-OLT authentication succeeds, the OLT CT + +calculates the MSK and the derivative shared keys, storing them for future use. Once the key calculation is completed, the OLT CT proceeds with execution of the authentication procedure by writing the OLT CT authentication result table and OLT CT result status to the ONU. + +Upon receipt of the OLT CT's response, the ONU verifies the OLT CT's authentication status and fills in the ONU authentication state attribute. The ONU transmits an attribute value change (AVC) on the ONU authentication state attribute. If the unidirectional OLT-to-ONU authentication has failed, a message integrity check (MIC) on the AVC message is generated using the previously active OMCI\_IK. If the unidirectional OLT-to-ONU authentication has succeeded (and thus the mutual authentication has succeeded as well), the MIC field on the AVC message is generated with the new OMCI\_IK. The new OMCI\_IK is committed active at the ONU. + +When the OLT CT receives the AVC on the ONU authentication state from the ONU, it checks whether the MIC field has been generated using the old OMCI\_IK or the new OMCI\_IK. If the old OMCI\_IK was used by the ONU, the OLT CT discards the previously calculated key material. If the new OMCI\_IK was used by the ONU, the OLT CT commits the new OMCI\_IK as active. The OLT CT then initiates a PLOAM handshake by generating a downstream Request\_Registration PLOAM message to the ONU. The purpose of the handshake is to delineate the activation of the secure shared keys in case of authentication success, or to obtain the registration-based MSK and derived shared keys in case of authentication failure. The Request\_Registration PLOAM message is protected, by definition, using the default PLOAM\_IK. Upon transmission of the Request\_Registration message, the OLT CT commits the new PLOAM\_IK as active on transmit. + +Once the ONU receives the downstream Request\_Registration PLOAM message, it generates an upstream Registration PLOAM message, which is protected, by definition, using the default PLOAM\_IK. Upon transmission of the Registration message, the ONU commits the new PLOAM\_IK and KEK as active. + +Once the OLT CT receives the upstream Registration PLOAM message from the ONU, it commits the PLOAM\_IK and KEK as active on receive, thus completing the key switching procedure. + +##### **B.11.5.3 Key switching for IEEE 802.1x-based authentication** + +Once the IEEE 802.1x-based mutual authentication or re-authentication process has completed, the OLT CT and the authenticated ONU have a 200 ms grace interval to compute the new set of derived shared keys. Within this interval, a sender should either remain silent or continue to use the old integrity key and switch to the new one as soon as it detects the new key in the received message, or at the end of the grace interval, at the latest. While the new key is being computed, a receiver continues checking the received messages with the old key. When the new key becomes available, the receiver should start checking messages with both old and new keys and switch to using the new key only once the new key check is successful, or at the end of the grace interval, at the latest. + +##### **B.11.5.4 MIC failure considerations** + +If MIC failure is caused by random transmission errors, then it is likely a rare event that can be correlated with the observed bit error ratio (BER) level. A persistent MIC failure, on the other hand, is likely caused by an integrity key mismatch at the transmitter and receiver and may indicate either a security threat or a malfunction of the authentication and key generation procedure. In case of persistent message integrity check failure, of which the OLT CT learns either directly (upstream MIC failure) or through the lack of expected management traffic flow from the ONU (downstream MIC failure), the OLT CT recognizes a loss of PLOAM channel (LOPCi) defect or a loss of OMCC channel (LOOCi) defect for a given ONU and has to select, at its discretion, the appropriate mitigation actions. These mitigation actions may include repeating authentication using the same or an alternative mechanism, blocking upstream and downstream traffic, deactivating or disabling the offending ONU, or executing a rogue ONU diagnostic procedure. + +### B.12 Power management + +WRP will provide the best user and network energy efficiency experience combining sleep periods behaviours when the link is idle (derived from the ITU-T PON watchful sleep and [b-IEEE 802.3az]), plus line rates switching during low duty periods according to the actual payload to be conveyed, enabling the logic at its ends to adapt the clock rate to the necessary throughput. + +#### B.12.1 Sleep mode + +During sleep modes bi-directional connectivity between both ends of the link will be temporarily lost. This clause is for further study. + +#### B.12.2 Line rate switching + +Line rate switching (LRS) is optional, since not all of the payload to be conveyed can support LRS when no similar hierarchy of line rates are applicable (e.g., lowest rate only ONUs) or when the interfaces cannot support any variation in payload (e.g., incompatibility with CPRI based fronthaul). + +LRP protocol is required to support unidirectional switching, to also provide the best efficiency for asymmetric traffic. + +A classical figure of merit widely used in network planning to start upgrading any link was 85% of the capacity. Therefore, the following thresholds over an observing period (OP) are considered: + +- Switching from low speed to its next step will occur when the effective payload crosses the threshold of 85% of its capacity. +- Reversely the switching down will occur when the effective payload (EP) is lower than 85% of this lower speed link capacity. + +The LRS state machine is shown in Figure B.11 using the 85% capacity threshold as an example. + +NOTE – The term "effective payload" excludes idle patterns from actual payload. + + + +``` +stateDiagram-v2 + [*] --> WS: No incoming traffic, no WS wake up, no clocking req + WS --> WS: No incoming traffic over OP. No clock req + WS --> Low_duty: EP < 85 % and no low latency payload, WS wake up or simple clocking req + WS --> Full_duty: EP > 85% of medium rate with low latency payload + Low_duty --> Low_duty: No threshold crossing over OP + Low_duty --> WS: EP < 85 % of low rate over OP + Low_duty --> Medium_duty: EP > 85% of low rate or req for lower latency + Medium_duty --> Medium_duty: No threshold crossing over OP + Medium_duty --> Low_duty: EP < 85% of medium rate over OP + Medium_duty --> Full_duty: EP > 85% of medium rate or req for lower latency + Full_duty --> Full_duty: No threshold crossing over OP + Full_duty --> WS: EP > 85% of medium rate with low latency payload +``` + +The diagram illustrates the LRS state machine with four states: Watchful sleep (WS), Low duty (min rate), Medium duty (med rate), and Full duty (max rate). Transitions are triggered by specific conditions related to effective payload (EP) and latency requirements. The initial state is WS, which can self-loop if there is no incoming traffic. Transitions to Low duty occur if EP < 85% and no low latency payload is required, or if a wake-up or clocking request is made. Transitions to Full duty occur if EP > 85% of medium rate with low latency payload. Low duty can self-loop if no threshold crossing over OP, transition to WS if EP < 85% of low rate over OP, or transition to Medium duty if EP > 85% of low rate or a request for lower latency is made. Medium duty can self-loop if no threshold crossing over OP, transition to Low duty if EP < 85% of medium rate over OP, or transition to Full duty if EP > 85% of medium rate or a request for lower latency is made. Full duty can self-loop if no threshold crossing over OP or transition to WS if EP > 85% of medium rate with low latency payload. + +Figure B.11 – LRS state machine diagram showing four states: Watchful sleep (WS), Low duty (min rate), Medium duty (med rate), and Full duty (max rate). Transitions are based on effective payload (EP) thresholds (85%) and latency requirements. + +Figure B.11 – LRS state machine + +### B.13 System protection + +This clause is for further study. + +## Annex C + +## **Secure mutual authentication via OMCI** + +(This annex forms an integral part of this Recommendation.) + +This is the same as Annex C of [ITU-T G.987.3]. + +## **Annex D** + +## **Secure mutual authentication using IEEE 802.1X** + +(This annex forms an integral part of this Recommendation.) + +This is the same as Annex D of [ITU-T G.987.3]. + +## Annex E + +## Transcoded mode management channel implementation + +(This annex forms an integral part of this Recommendation.) + +A transcoder byte replacement mechanism can be used for 64B/66B framing 25Gbit/s Ethernet transmission in WDM PON system, realizing the multiplexing of WDM PON management data and user data. The 64B/66B line coding and corresponding code format for 25G are specified in clause 49, clause 107 and clause 113 of [b-IEEE 802.3]. + +At the transmitter, the framed WDM PON management TC data and user data are transmitted to the transcoder. The 64B/66B coding bytes transformed from preamble are sequentially replaced by framed WDM PON management TC data. + +At the receiver, the transcoder sequentially extracts the framed WDM PON management TC data from the bytes corresponding to preamble and passes them to the management TC framing sublayer. The default values of the original bytes corresponding to preamble will be recovered. + +Different control codes in block type field are used to indicate the control character of the control block. For preamble, three control codes defined in clause 49.2.4.4 [b-IEEE 802.3] can take values of 0x78, 0x33 or 0x66. Three block type fields are defined below showing their respective data and control character mapping implementation: + +- 1) A block type field of 0x78 ( $S_0D_1D_2D_3/D_4D_5D_6D_7$ ): consists of a Start byte ( $S_0$ ), seven free bytes from $D_1$ to $D_7$ , where $D_1$ is the identifier followed by six bytes used as framed WDM PON management TC data carrier; +- 2) A block type field of 0x33 ( $C_0C_1C_2C_3/S_4D_5D_6D_7$ ): consists of four valid control characters ( $C_0$ to $C_3$ ), a start byte $S_4$ , three free bytes from $D_5$ to $D_7$ , followed by 4 bytes in the next block. Here $D_5$ is the identifier. $D_6$ , $D_7$ and four bytes from the next block are used framed WDM PON management TC data carrier; +- 3) A block type field of 0x66 ( $O_0D_1D_2D_3/S_4D_5D_6D_7$ ): consist of and a valid O code, three free bytes from $D_5$ to $D_7$ , followed by 4 bytes in the next block. Here $D_5$ is an identifier. $D_6$ , $D_7$ and four bytes from the next block are used as framed WDM PON management TC data carrier. + +If no user data is transmitted (i.e., none of 0x78/0x33/0x66), the pure control represented control code 0x1E ( $C_0C_1C_2C_3/C_4C_5C_6C_7$ , as IDLE) will be transformed to 0x78 in the transmitter of the transcoder. The value of parameter C of the corresponding identification byte $D_0$ will be set as "1", and the management data replacement will be continued as in the case block type field is 0x78. + +Therefore, in the receiver, when control block has a block type field of 0x78, and the value of parameter C of the corresponding identification byte is "1", the 7 bytes from $D_1$ to $D_7$ will be extracted sequentially and passed to the management TC framing sublayer. The default values of the original bytes corresponding to preamble will be recovered. + +The $D_0$ identifier indicates the feature of the replaced WRP management data in respective block, the identification byte is specified in Table E.1. + +**Table E.1 – Identification byte of the control block identifier** + +| Octet | Parameter | Description | +|-----------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1-2 (LSB) | AB | 00 – framed WDM PON management TC data is included in the following 6 bytes
01 – synchronization pattern is included in the following 2 bytes, the other bytes are reserved
10 – disabled
11 – IDLE | +| 3 | C | 0 – original control code
1 –transformed control code from 0x1E | +| 4-8 | DEFGH | Reserved. | + +## Annex F + +## Services with 25G eCPRI over Ethernet + +(This annex forms an integral part of this Recommendation.) + +The interface of eCPRI is specified in [b-eCPRI]. PHY and media access control (MAC) layer of 25G eCPRI services are 25G Ethernet based. clause 108 of [b-IEEE 802.3] specify the Reed-Solomon forward error correction (RS-FEC) for 25GBASE-R PHYs. In order to support codeword alignment in the receive direction, the 25GBASE-R RS-FEC shall periodically insert codeword markers into the stream of transcoded blocks as the first 257 bits of every 1024th RS-FEC codeword. The distance between the beginning of successive codeword markers is therefore 20480 257-bit transcoded blocks, equivalent to 81920 64B/66B blocks. The transmitted codeword marker is a 257-bit block, constructed of four alignment markers followed by a zero bit. Each alignment marker is built from eight octets. Figure F.1 shows the processing of RS-FEC function in the physical coding sublayer (PCS) sublayer. + + + +Figure F.1 – Processing of PCS sublayer. This block diagram illustrates the data flow from input to output through several processing stages. At the top, an input stream is shown as a sequence of four 65-bit blocks: '0 tx\_coded\_0 65', '0 tx\_coded\_1 65', '0 tx\_coded\_2 65', and '0 tx\_coded\_3 65'. An arrow labeled 'From codeword marker rate compensation' points to the end of this sequence. The stream enters a '64B/66B to 256B/257B transcoder' block. The output is a 'tx\_scrambled' stream, shown as a 256-bit block with bits '0' and '256' at the ends. A 'tx\_cwm' (codeword marker) is inserted into this stream. The next stage is 'Codeword marker insertion', which produces a 'Message' block. This message has a 257-bit length, with bits '0' and '256' at the ends. It includes alignment markers: m\_513 at bit 0, m\_512 at bit 9, m\_0 at bit 256, and m\_511 at bit 257. The message is then processed by a 'Reed-Solomon encoder'. The output is a 'Codeword' block, also 257 bits long (bits 0 to 256). It contains the message data and parity bits: c\_527 = m\_513 at bit 0, c\_526 = m\_512 at bit 9, c\_14 = m\_0 at bit 256, c\_13 = p\_13 at bit 257, and c\_0 = p\_0 at bit 258. Finally, the codeword is processed by a 'Serialization' block, which outputs the final stream. A reference label 'G.9802.2(23)' is at the bottom right. + +Figure F.1 – Processing of PCS sublayer + +For 25G eCPRI, there is only one lane, so one alignment marker is used, and the other three alignment makers are filled with fixed pattern but not used. For WDM PON system that supports 25G eCPRI, these unused bits can be used to management channel. In order to keep as close to the standardized 25G BASE-R PHY as possible, the alignment marker is inconsistent with the alignment marker of PCS + +lane 0 specified in [b-IEEE 802.3], and the other three 64-bit blocks are used as management channel. Thus, the maximal amount of WDM PON management information to be sent is 192 bits per codeword marker. As the management channel of WDM PON system is not always working, the first 2 bits of these 192 bits are used as message indicator and the remaining 190 bits are OAM content. Figure F.2 shows the format of codeword marker for WDM PON system. + + + +The diagram illustrates the structure of a codeword marker in a WDM PON system. At the top, a horizontal bar represents a sequence of 1024 codewords, with a 'CM' (Codeword marker) block at the start and end. Below this, a detailed view of the codeword marker is shown. It consists of a '0' bit field, followed by an 'Alignment marker (64 bits)', three 'Management (64 bits)' blocks, and finally a 'MI' (Message indicator) followed by 'OAM content'. Arrows indicate the relationship between the top-level codeword sequence and the detailed marker structure. + +CM: Codeword marker MI: Message indicator G.9802.2(23) + +Diagram of codeword marker format for WDM PON system. The top part shows a sequence of 1024 codewords with a Codeword marker (CM) at the beginning and end. The bottom part shows a detailed view of the codeword marker structure: a 0-bit field, an Alignment marker (64 bits), three Management (64 bits) blocks, and a Message indicator (MI) followed by OAM content. + +**Figure F.2 – Codeword marker for WDM PON system** + +**MI** (message indicator) is a 2-bit field that indicates whether the OAM content field is valid. It has following encoding: + +- 00: the OAM content is invalid; +- 01: reserved; +- 10: reserved; +- 11: the OAM content is valid. + +For WDM PON system with 25G eCPRI or other 25GE based services, codeword marker is inserted every 1024 RS (528,514) [b-IEEE 802.3] codewords. At the transmitter side, the PCS receives 81920 64B/66B blocks and transcodes them to 20480 257-bit transcoded blocks, and generates one codeword marker. The codeword marker with alignment marker, message indicator and message content are encoded together with received data blocks. At the receive side, the PCS can realize the codewords synchronization based on the 64 bits alignment marker. + +# **Annex G** + +## **Hybrid error control (HEC) decoding and scrambler sequence codes** + +(This annex forms an integral part of this Recommendation.) + +This is the same as Annex A of [ITU-T G.987.3]. + +## Bibliography + +- [b-ITU-T G.698.4] Recommendation ITU-T G.698.4 (2023), *Multichannel bi-directional DWDM applications with port agnostic single-channel optical interfaces.* +- [b-ITU-T G.959.1] Recommendation ITU-T G.959.1 (2018), *Optical transport network physical layer interfaces.* +- [b-ITU-T G.989] Recommendation ITU-T G.989 (2015), *40-Gigabit-capable passive optical networks (NG-PON2): Definitions, abbreviations and acronyms.* +- [b-ITU-T G.9802.1] Recommendation ITU-T G.9802.1 (2021), *Wavelength division multiplexed passive optical networks (WDM PON): General requirements.* +- [b-ITU-T G.Sup39] Recommendation ITU-T G.Sup39 (2016), *Optical system design and engineering considerations.* +- [b-ATIS-0300220] ATIS-0300220 (2016), *Structure for the Representation of the Communications Industry Manufacturers, Suppliers, and Related Service Companies for Information Exchange.* +- [b-eCPRI] eCPRI Specification V2.0 (2019-05-10), *Common Public Radio Interface: eCPRI Interface Specification.* +- [b-IEEE 802.3-2018] IEEE Std 802.3-2018, *IEEE Standard for Ethernet.* +- [b-IEEE 802.3-2022] IEEE Standard for Ethernet, in IEEE Std 802.3-2022 (Revision of IEEE Std 802.3-2018). +- [b-IEEE 802.3az] IEEE Standard IEEE 802.3az-2010, *IEEE Standard for Information technology – Local and metropolitan area networks – Specific requirements – Part 3: CSMA/CD Access Method and Physical Layer Specifications Amendment 5: Media Access Control Parameters, Physical Layers, and Management Parameters for Energy-Efficient Ethernet.* +- [b-NIST FIPS-197] NIST Federal Information Processing Standards Publication 197 (2001), *Advanced Encryption Standard (AES).* +- [b-NIST SP800-38B] NIST Special Publication 800-38B (2016), *Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication.* + + + + + +## 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.984.2-201908-I_PDF-E/114a0f7c7ac69ab82f03d68650cf8e88_img.jpg b/marked/G/T-REC-G.984.2-201908-I_PDF-E/114a0f7c7ac69ab82f03d68650cf8e88_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac824a95c236b666b76a6506d546709ba3789ddf --- /dev/null +++ b/marked/G/T-REC-G.984.2-201908-I_PDF-E/114a0f7c7ac69ab82f03d68650cf8e88_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be3f7e4f1f45161febeb8db70dd86247bfaea941bdf253820ddd1cbd0042bdfc +size 11883 diff --git a/marked/G/T-REC-G.984.2-201908-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.984.2-201908-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827609df9ad8667ae079f875841506349f063390 --- /dev/null +++ b/marked/G/T-REC-G.984.2-201908-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0d2afb537db9f3588854962a991eb1178220b2bbb8ff3cea6712979a53a864b +size 4107 diff --git a/marked/G/T-REC-G.984.2-201908-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg b/marked/G/T-REC-G.984.2-201908-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69b8c58eb5f3154142aafeff8f83c113e0d357d0 --- /dev/null +++ b/marked/G/T-REC-G.984.2-201908-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e4911be646a68766fcf4e6d5ea90585c4fbfc4d2fc9f1f1958413b5e3ec56a2 +size 37691 diff --git a/marked/G/T-REC-G.984.2-201908-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg b/marked/G/T-REC-G.984.2-201908-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60898fc736caba215753f9b5739d270f4ce435f5 --- /dev/null +++ b/marked/G/T-REC-G.984.2-201908-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f86f0030d1972f829c4edef9055ff173522e6b432c4f0873defa4f9c5bcaad63 +size 39320 diff --git a/marked/G/T-REC-G.984.2-201908-I_PDF-E/51536f203c07ce20ce119e7e09b11cb6_img.jpg b/marked/G/T-REC-G.984.2-201908-I_PDF-E/51536f203c07ce20ce119e7e09b11cb6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..156e143bd6bcd5cd77c1e2b100fddec3e6801bd9 --- /dev/null +++ b/marked/G/T-REC-G.984.2-201908-I_PDF-E/51536f203c07ce20ce119e7e09b11cb6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3229bf82c4e8178987e300d5876a42c50718e60da34f479c8eb39570abcc551 +size 17235 diff --git a/marked/G/T-REC-G.984.2-201908-I_PDF-E/80ec3bf791fd8eb41f73a420c2122529_img.jpg b/marked/G/T-REC-G.984.2-201908-I_PDF-E/80ec3bf791fd8eb41f73a420c2122529_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9743595dccf131ed04fbafb4d425f93803b13d3 --- /dev/null +++ b/marked/G/T-REC-G.984.2-201908-I_PDF-E/80ec3bf791fd8eb41f73a420c2122529_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c7547ea9173a9034812d2159f0287c10cf8f39699abbca53626dda33996850e +size 30891 diff --git a/marked/G/T-REC-G.984.2-201908-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/marked/G/T-REC-G.984.2-201908-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebce38996f8194cc08efaad5a8b78d35e132867f --- /dev/null +++ b/marked/G/T-REC-G.984.2-201908-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:009f5cd977ef6ccf5a3f5eb24922879e259e067c2962f69912f94ab74f7a2797 +size 20450 diff --git a/marked/G/T-REC-G.984.2-201908-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg b/marked/G/T-REC-G.984.2-201908-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4e72e70264117cad33e16fe07bafa131ed5991c --- /dev/null +++ b/marked/G/T-REC-G.984.2-201908-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8394c59b0e0adf174b7bff1ecd48a9549dd50dd513e2bc1b57b74b3e954e973f +size 20057 diff --git a/marked/G/T-REC-G.984.2-201908-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg b/marked/G/T-REC-G.984.2-201908-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea0e441bf598046d6c1e6609c2292dea8e13ed85 --- /dev/null +++ b/marked/G/T-REC-G.984.2-201908-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9b636b8bbdb432f20fba60b18a3462854f6eabfe7469e1620346079e02646ec +size 35311 diff --git a/marked/G/T-REC-G.984.2-201908-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/G/T-REC-G.984.2-201908-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1e875bd02324d32a61e814262cd7a394bf4fc03 --- /dev/null +++ b/marked/G/T-REC-G.984.2-201908-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1edcab3151bc00840dd376d4df95392dfc2367339ddee1cb5315d9d59a6c1d0 +size 37926 diff --git a/marked/G/T-REC-G.984.2-201908-I_PDF-E/raw.md b/marked/G/T-REC-G.984.2-201908-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8b8eb97e51ad636324a227802966cc5723f72400 --- /dev/null +++ b/marked/G/T-REC-G.984.2-201908-I_PDF-E/raw.md @@ -0,0 +1,1493 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.984.2** + +(08/2019) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital sections and digital line system – Optical line +systems for local and access networks + +--- + +**Gigabit-capable passive optical networks +(GPON): Physical media dependent (PMD) layer +specification** + +Recommendation ITU-T G.984.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 | +| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | +| General | G.900–G.909 | +| Parameters for optical fibre cable systems | G.910–G.919 | +| Digital sections at hierarchical bit rates based on a bit rate of 2048 kbit/s | G.920–G.929 | +| Digital line transmission systems on cable at non-hierarchical bit rates | G.930–G.939 | +| Digital line systems provided by FDM transmission bearers | G.940–G.949 | +| Digital line systems | G.950–G.959 | +| Digital section and digital transmission systems for customer access to ISDN | G.960–G.969 | +| Optical fibre submarine cable systems | G.970–G.979 | +| Optical line systems for local and access networks | G.980–G.989 | +| Metallic access networks | G.990–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.984.2 + +# Gigabit-capable passive optical networks (GPON): Physical media dependent (PMD) layer specification + +## Summary + +Recommendation ITU-T G.984.2 describes a flexible optical fibre access network capable of supporting the bandwidth requirements of business and residential services, and covers systems with nominal line rates of 1 244.160 Mbit/s and 2 488.320 Mbit/s in the downstream direction and 155.520 Mbit/s, 622.080 Mbit/s, 1 244.160 Mbit/s and 2 488.320 Mbit/s in the upstream direction. Both symmetrical and asymmetrical (upstream/downstream) gigabit-capable passive optical network (GPON) systems are described. This Recommendation proposes the physical layer requirements and specifications for the physical media dependent (PMD) layer. The transmission convergence (TC) layer and ranging protocol for GPON systems are described in Recommendation ITU-T G.984.3. + +This Recommendation describes a system that represents an evolutionary development from the system described in ITU-T G.983.1. To the greatest extent possible, this Recommendation maintains the requirements of ITU-T G.983.1 to ensure maximal continuity with existing systems and optical fibre infrastructure. In addition, it describes several enhanced optical budgets (B+, C+, and D) to extend that capability. The necessary parameters are defined to support optical layer supervision. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|-----------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.984.2 | 2003-03-16 | 15 | 11.1002/1000/6273 | +| 1.1 | ITU-T G.984.2 (2003) Amd. 1 | 2006-02-17 | 15 | 11.1002/1000/8746 | +| 1.2 | ITU-T G.984.2 (2003) Amd. 2 | 2008-03-29 | 15 | 11.1002/1000/9380 | +| 2.0 | ITU-T G.984.2 | 2019-08-29 | 15 | 11.1002/1000/14000 | + +## Keywords + +GPON, PMD. + +--- + +\* To access the Recommendation, type the URL
GPON class B+ ..... | | 26 | +| A.1 | Introduction ..... | 26 | +| A.2 | System applications ..... | 26 | +| A.3 | Optical specifications ..... | 26 | +| A.4 | Link budget..... | 27 | +| Annex B – Description of physical layer measurements to support optical layer
supervision..... | | 29 | +| B.1 | Introduction ..... | 29 | +| B.2 | Transceiver parameters monitoring..... | 29 | +| B.3 | Measurement table for transceiver parameters..... | 29 | +| B.4 | OLS physical layer performance measurements requirements ..... | 30 | +| Appendix I – Allocation of the physical layer overhead time ..... | | 31 | +| Appendix II – Description and examples of power levelling mechanism ..... | | 33 | +| II.1 | Introduction ..... | 33 | +| II.2 | ONU levels ..... | 33 | +| II.3 | Thresholds at OLT ..... | 33 | +| II.4 | Power detection ..... | 35 | +| Appendix III..... | | 36 | +| Appendix IV ..... | | 37 | +| Appendix V – Industry best practice for single-sided extended 2.488 Gbit/s downstream,
1.244 Gbit/s upstream GPON (class C+ and class D) ..... | | 38 | +| V.1 | Introduction ..... | 38 | +| Bibliography..... | | 41 | + + + +## Recommendation ITU-T G.984.2 + +# Gigabit-capable passive optical networks (GPON): Physical media dependent (PMD) layer specification + +# 1 Scope + +This Recommendation describes flexible access networks using optical fibre technology. The focus is primarily on a network supporting services with bandwidth requirements ranging from that of voice to gigabit-per-second data services. Also included are distributive services. + +This Recommendation describes characteristics of the physical media dependent (PMD) layer of an optical access network (OAN) with the capability of transporting various services between the user-network interface and the service node interface (SNI). + +The OAN dealt within this Recommendation should enable the network operator to provide a flexible upgrade to meet future customer requirements, in particular, in the area of the optical distribution network (ODN). The ODN considered is based on a point-to-multipoint tree and branch option. + +This Recommendation concentrates on the fibre issues: the copper issues of hybrid systems are described elsewhere, e.g., in Recommendations on any type of digital subscriber line (xDSL) (ITU-T G.99x-series). + +This Recommendation focuses on additions to and modifications of earlier members of the ITU-T G.983.x series, which describe an architecture based on the asynchronous transfer mode (ATM) over a passive optical network (PON). The purpose of the additions and modifications are to support higher data rates, especially for the transport of data services. + +This Recommendation proposes the physical layer requirements and specifications for the PMD layer of a gigabit-capable passive optical network (GPON). The transmission convergence (TC) layer and ranging protocol specifications for GPON systems are specified in [ITU-T G.984.3]. + +# 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 G.652 (2016), *Characteristics of a single-mode optical fibre cable*. +- [ITU-T G.982] Recommendation G.982 (1996), *Optical access networks to support services up to the ISDN primary rate or equivalent bit rates*. +- [ITU-T G.983.1] Recommendation G.983.1 (2005), *Broadband optical access systems based on Passive Optical Networks (PON)*. +- [ITU-T G.983.3] Recommendation G.983.3 (2001), *A broadband optical access system with increased service capability by wavelength allocation*. +- [ITU-T G.984.1] Recommendation G.984.1 (2008), *Gigabit-capable passive optical networks (GPON): General characteristics*. + +- [ITU-T G.984.3] Recommendation G.984.3 (2014), *Gigabit-capable passive optical networks (GPON): Transmission convergence layer specification*. +- [ITU-T G.984.5] Recommendation G.984.5 (2014), *Gigabit-capable passive optical networks (G-PON): Enhancement band*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 accuracy of a measuring system (accuracy):** This is the ability of a measuring system to provide an indication value that is close to the true value being measured. This is normally expressed as an error range around the true value. + +**3.2.2 optical access network (OAN):** The set of access links sharing the same network-side interfaces and supported by optical access transmission systems. The OAN may include a number of ODNs connected to the same OLT. + +**3.2.3 optical distribution network (ODN):** In the pon context, a tree of optical fibres in the access network, supplemented with power or wavelength splitters, filters or other passive optical devices. + +**3.2.4 optical line supervision (OLS):** A set of capabilities relating to the measurement and reporting of the state of the optical link. + +**3.2.5 optical line termination (OLT):** A device that terminates the common (root) endpoint of an ODN, implements a PON protocol, such as that defined by [ITU-T G.984.3], and adapts PON PDUs for uplink communications over the provider service interface. The OLT provides management and maintenance functions for the subtended ODN and ONUs. + +**3.2.6 optical network termination (ONT):** A single subscriber device that terminates any one of the distributed (leaf) endpoints of an ODN, implements a PON protocol, and adapts PON PDUs to subscriber service interfaces. An ONT is a special case of an ONU. + +**3.2.7 optical network unit (ONU):** A generic term denoting a device that terminates any one of the distributed (leaf) endpoints of an ODN, implements a PON protocol, and adapts PON PDUs to subscriber service interfaces. In some contexts, an ONU implies a multiple subscriber device. + +**3.2.8 range of indications (range):** This term can be either called as "range of indications" or "indication intervals". It is the set of quantity values bounded by the extreme possible indications of a measuring system. + +**3.2.9 repeatability of a measuring system (repeatability):** This is the property of a measuring system to provide closely similar indications for replicated measurements of the same quantity under repeatable conditions. This is normally expressed as a range of indications that result from repeated measurements of identical conditions. + +**3.2.10 resolution of a measuring system (resolution):** This is the smallest change in the value of the quantity being measured by a measuring system that causes a perceptible change in the corresponding indication. + +**3.2.11 response time (RT):** For a measurement circuit, the time between test initiation and availability of a valid measurement. The RT does not include the delays associated with the transmission of the result to higher layers. The RT explains the real-time requirement for optical line supervision reasons. + +**3.2.12 time division multiple access (TDMA):** Transmission technique involving the multiplexing of many time slots onto the same time payload. + +**3.2.13 wavelength division multiplexing (WDM):** Bidirectional multiplexing using different optical wavelength for upstream and downstream signals. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------------| +| APD | Avalanche Photodiode | +| ATM | Asynchronous Transfer Mode | +| BER | Bit Error Ratio | +| BPON | Broadband Passive Optical Network | +| CID | Consecutive Identical Digit | +| DFB | Distributed Feedback | +| EMS | Element Management System | +| EX | Extinction ratio | +| FEC | Forward Error Correction | +| FFS | For Further Study | +| GPON | Gigabit-capable Passive Optical Network | +| ISDN | Integrated Services Digital Network | +| MLM | Multi-Longitudinal Mode | +| MPN | Mode Partition Noise | +| NRZ | Non-Return to Zero | +| OAN | Optical Access Network | +| ODN | Optical Distribution Network | +| OLS | Optical Line Supervision | +| OLT | Optical Line Termination | +| ONT | Optical Network Termination | +| ONU | Optical Network Unit | +| ORL | Optical Return Loss | +| PIN | Photodiode without Internal Avalanche | +| PMD | Physical Media Dependent | +| PON | Passive Optical Network | +| p-p | peak to peak | +| RMS | Root Mean Square | +| R/S | Receive/Send | +| RT | Response Time | +| Rx | Receiver | +| SLM | Single-Longitudinal Mode | + +| | | +|------|-------------------------------------| +| SNI | Service Node Interface | +| SOA | Semiconductor Optical Amplifier | +| S/R | Send/Receive | +| TC | Transmission Convergence | +| TDMA | Time Division Multiple Access | +| Tx | Transmission | +| UI | Unit Interval | +| WDM | Wavelength Division Multiplexing | +| xDSL | any type of Digital Subscriber Line | + +# 5 Architecture of the optical access network + +See [ITU-T G.983.1]. For convenience, Figure 5 of [ITU-T G.983.1] is reproduced in Figure 1. + + + +Figure 1 – Generic physical configuration of the optical distribution network. The diagram shows an Optical Line Terminal (OLT) on the right connected to an Optical Distribution Network (ODN) in the center. The ODN is connected to multiple Optical Network Units (ONUs), labeled ONU1 and ONU\_n, on the left. Reference points R/S are shown at the top of each ONU and at the top of the OLT. Optical interfaces are labeled O\_rd, O\_ru at the ONUs and O\_ld, O\_lu at the OLT. A legend at the bottom left defines the symbols: solid lines for 'R and S Reference points' and 'O\_rd, O\_ru, O\_ld, O\_lu Optical interfaces'; solid lines for 'Represent one or more fibre'; and dotted lines for 'Represent optional protection fibres'. The diagram is labeled G.984.2\_F01. + +**Figure 1 – Generic physical configuration of the optical distribution network** + +The two directions for optical transmission in the ODN are identified as follows: + +- downstream direction for signals travelling from the OLT to the ONU(s); +- upstream direction for signals travelling from the ONU(s) to the OLT. + +Transmission in downstream and upstream directions can take place on the same fibre and components (duplex/diplex working) or on separate fibres and components (simplex working). + +# 6 Services + +See [ITU-T G.984.1]. + +# 7 User network interface and service node interface + +See [ITU-T G.984.1]. + +# 8 Optical network requirements + +## 8.1 Layered structure of optical network + +See [ITU-T G.983.1] and [ITU-T G.983.3]. + +## 8.2 Physical medium dependent layer requirements for the GPON + +### 8.2.1 Digital signal nominal bit rate + +The transmission line rate should be a multiple of 8 kHz. The target standardized system will have nominal line rates (downstream/upstream) of: + +- 1 244.16 Mbit/s/155.52 Mbit/s, +- 1 244.16 Mbit/s/622.08 Mbit/s, +- 1 244.16 Mbit/s/1 244.16 Mbit/s, +- 2 488.32 Mbit/s/155.52 Mbit/s, +- 2 488.32 Mbit/s/622.08 Mbit/s, +- 2 488.32 Mbit/s/1 244.16 Mbit/s, +- 2 488.32 Mbit/s/2 488.32 Mbit/s. + +Parameters to be determined are categorized by downstream and upstream, and nominal bit rate as shown in Table 1. + +**Table 1 – Relation between parameter categories and tables** + +| Transmission direction | Nominal bit rate
(Mbit/s) | Table | +|------------------------|------------------------------|----------------------------------------------------------------------------| +| Downstream | 1 244.16 | Table 2b (downstream, 1 244 Mbit/s) | +| | 2 488.32 | Table 2c (downstream, 2 488 Mbit/s) | +| Upstream | 155.52 | Table 2d (upstream, 155 Mbit/s) | +| | 622.08 | Table 2e (upstream, 622 Mbit/s) | +| | 1 244.16 | Table 2f-1 (upstream, 1 244 Mbit/s)
Table 2f-2 (upstream, 1 244 Mbit/s) | +| | 2 488.32 | Table 2g-1 (upstream, 2 488 Mbit/s)
Table 2g-2 (upstream, 2 488 Mbit/s) | + +All parameters are specified as follows, and shall be in accordance with Table 2a (ODN) and Table 2b to g-2. There is a separate type of ONU for each combination of upstream bit-rate, downstream bit-rate and optical path loss class (class A, B, or C as specified in [ITU-T G.982]). + +All parameter values specified 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 $1 \times 10^{-10}$ for the extreme case of optical path attenuation and dispersion conditions. + +In particular, the values in this Recommendation, in Table 2b to g-2, are valid for the cases without an enhancement band, as described in [ITU-T G.983.3]. For GPONs with enhancement band applications, a new set of parameters must be defined, together with requirements for isolation between the different wavelength bands. This can be described in a separate Recommendation, having the same relation to this Recommendation as [ITU-T G.983.3] has to [ITU-T G.983.1]. However, the optical wavelength specified in this Recommendation for the downstream direction complies with [ITU-T G.983.3], in order to allow a smooth integration of the enhancement band in the future. + +### 8.2.2 Physical media and transmission method + +#### 8.2.2.1 Transmission medium + +This Recommendation is based on the fibre specified in [ITU-T G.652]. + +#### 8.2.2.2 Transmission direction + +The signal is transmitted both upstream and downstream through the transmission medium. + +#### 8.2.2.3 Transmission methodology + +Bidirectional transmission is accomplished by use of either the wavelength division multiplexing (WDM) technique on a single fibre or unidirectional transmission over two fibres (see clause 8.2.5). + +### 8.2.3 Bit rate + +This clause deals with bit-rate requirements for the GPON. + +#### 8.2.3.1 Downstream + +The nominal bit rate of the OLT-to-ONU signal is 1 244.16, or 2 488.32 Mbit/s. When the OLT and the end office are in their normal operating state, this rate is traceable to a stratum-1 clock (accuracy of $1 \times 10^{-11}$ ). When the end office is in its free-running mode, the rate of the downstream signal is traceable to a stratum-3 clock (accuracy of $4.6 \times 10^{-6}$ ). When the OLT is in its free-running mode, the accuracy of the downstream signal is that of a stratum-4 clock ( $3.2 \times 10^{-5}$ ). + +NOTE – The OLT may source its timing from either a dedicated timing signal source or from a synchronous data interface (line timing). A packet-based timing source may also be used. + +#### 8.2.3.2 Upstream + +The nominal bit rate of the ONU-to-OLT signal is 155.52, 622.08, 1 244.16, or 2 488.32 Mbit/s. When in one of its operating states and given a grant, the ONU shall transmit its signal with an accuracy equal to that of the received downstream signal. The ONU shall not transmit any signal when not in one of its operating states or when not given a grant. + +### 8.2.4 Line code + +Downstream and upstream: non-return to zero (NRZ) coding. + +Scrambling method not defined at the PMD layer. + +Convention used for optical logic level is: + +- high level of light emission for a binary "1"; +- low level of light emission for a binary "0". + +### 8.2.5 Operating wavelength + +#### 8.2.5.1 Downstream direction + +The operating wavelength range for the downstream direction on single fibre systems shall be 1 480-1 500 nm. + +The operating wavelength range for the downstream direction on two fibre systems shall be 1 260-1 360 nm. + +#### 8.2.5.2 Upstream direction + +The operating wavelength range for the upstream direction shall be 1 260-1 360 nm. + +### 8.2.6 Transmitter at Old and Oru + +All parameters are specified as follows, and shall be in accordance with Table 2. + +#### 8.2.6.1 Source type + +See clause 8.2.6.1 of [ITU-T G.983.1]. + +#### 8.2.6.2 Spectral characteristics + +See clause 8.2.6.2 of [ITU-T G.983.1]. + +#### 8.2.6.3 Mean launched power + +The mean launched power at $O_{\text{ld}}$ and $O_{\text{ru}}$ 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 all allowances for operation under standard operating conditions, transmitter connector degradation, measurement tolerances and ageing effects. + +In the operating state, the lower figure is the minimum power that shall be provided and the higher one is the power that shall never be exceeded. + +NOTE – The measurement of the launched power at the $O_{\text{ru}}$ optical interface shall take into account the bursty nature of the upstream traffic transmitted by the ONUs. + +###### 8.2.6.3.1 Launched optical power without input to the transmitter + +In the upstream direction, the ONU transmitter should launch no power into the fibre in all slots that are not assigned to that ONU. However, an optical power level less than or equal to the launched power without input to the transmitter, specified in Table 2d to g-1, is allowed. The ONU shall also meet this requirement during the guard time of slots that are assigned to it, with the exception of the last transmission (Tx) enable bits which may be used for laser pre-bias, and the Tx disable bits immediately following the assigned cell, during which the output falls to zero. The maximum launched power level allowed during laser pre-bias is the zero level corresponding to the extinction ratio (EX) specified in Table 2d to g-1. + +The specification of the maximum number of Tx enable and Tx disable bits for each upstream bit rate is provided in Table 2d to g-1. + +#### 8.2.6.4 Minimum extinction ratio + +The convention adopted for the optical logic level is: + +- high level of light emission for a logical "1"; +- low level of light emission for a logical "0". + +The EX is determined by: + +$$\text{EX} = 10 \log_{10} (A/B)$$ + +where $A$ is the average optical power level at the centre of the logical "1" and $B$ is the average optical power level at the centre of the logical "0". + +The EX for the upstream direction burst mode signal is applied from the first bit of the preamble to the last bit of the burst signal inclusive. This does not apply to any procedures related to the optical power set-up. + +#### 8.2.6.5 Maximum reflectance of equipment, measured at transmitter wavelength + +See clause 8.2.6.5 of [ITU-T G.983.1]. + +#### 8.2.6.6 Mask of transmitter eye diagram + +See clause 8.2.6.6 of [ITU-T G.983.1]. + +##### 8.2.6.6.1 OLT transmitter + +The parameters specifying the mask of the eye diagram are shown in Figure 2. + +##### **8.2.6.6.2 ONU transmitter** + +The parameters specifying the mask of the eye diagram are shown in Figure 3. + +The mask of the eye diagram for the upstream direction burst mode signal is applied from the first bit of the preamble to the last bit of the burst signal inclusive. This does not apply to any procedures related to the optical power set-up. + +#### **8.2.6.7 Tolerance to the reflected optical power** + +The specified transmitter performance must be met in the presence at S of the optical reflection level specified in Table 2. + +### **8.2.7 Optical path between Old/Oru and Ord/Olu** + +#### **8.2.7.1 Attenuation range** + +See clause 8.2.7.1 of [ITU-T G.983.1]. + +#### **8.2.7.2 Minimum optical return loss of the cable plant at point R/S, including any connectors** + +See clause 8.2.7.2 of [ITU-T G.983.1]. + +#### **8.2.7.3 Maximum discrete reflectance between points S and R** + +See clause 8.2.7.3 of [ITU-T G.983.1]. + +#### **8.2.7.4 Dispersion** + +See clause 8.2.7.4 of [ITU-T G.983.1]. + +### **8.2.8 Receiver at Ord and Olu** + +All parameters are specified in clauses 8.2.8.1 to 8.2.8.12, and shall be in accordance with Table 2. + +#### **8.2.8.1 Minimum sensitivity** + +See clause 8.2.8.1 of [ITU-T G.983.1]. + +#### **8.2.8.2 Minimum overload** + +See clause 8.2.8.2 of [ITU-T G.983.1]. + +#### **8.2.8.3 Maximum optical path penalty** + +The receiver is required to tolerate an optical path penalty not exceeding 1 dB to account for total degradations due to reflections, intersymbol interference, mode partition noise (MPN), and laser chirp. In the upstream direction, the specified laser types in Table 2 produce less than 1 dB of optical path penalty over the ODN. As indicated in Note 5 of Table 2e and f-1, an increase in the upstream optical path penalty due to dispersion at bit rates of 622 Mbit/s or above is acceptable, provided that any increase in optical path penalty over 1 dB is compensated by an increase of the minimum transmitted launch power, or an increase of the minimum receiver sensitivity. + +#### **8.2.8.4 Maximum logical reach** + +The maximum logical reach is defined as the maximum length that can be achieved for a particular transmission system independently of the optical budget. It is measured in kilometres and is not limited by PMD parameters, but rather TC layer and implementation issues. + +#### **8.2.8.5 Maximum differential logical reach** + +The differential logical reach is the maximum difference in logical reach among all ONUs. It is measured in kilometres and is not limited by PMD parameters but rather TC layer and implementation issues. + +#### **8.2.8.6 Maximum reflectance of receiver equipment, measured at receiver wavelength** + +See clause 8.2.8.4 of [ITU-T G.983.1]. + +#### **8.2.8.7 Differential optical path loss** + +See clause 8.2.8.5 of [ITU-T G.983.1]. + +#### **8.2.8.8 Clock extraction capability** + +See clause 8.2.8.6 of [ITU-T G.983.1]. + +#### **8.2.8.9 Jitter performance** + +This clause deals with jitter requirements for optical interfaces at the GPON. + +##### **8.2.8.9.1 Jitter transfer** + +Jitter transfer specification applies only to ONU. + +The jitter transfer function is defined as: + +$$\text{jitter transfer} = 20\log_{10} \left[ \frac{\text{jitter on upstream signal UI}}{\text{jitter on downstream signal UI}} \times \frac{\text{downstream bit rate}}{\text{upstream bit rate}} \right]$$ + +The jitter transfer function of an ONU shall be under the curve given in Figure 4, when input sinusoidal jitter up to the mask level in Figure 5 is applied, with the parameters specified therein for each bit rate. + +##### **8.2.8.9.2 Jitter tolerance** + +See clause 8.2.8.7.2 of [ITU-T G.983.1]. + +###### **8.2.8.9.3 Jitter generation** + +Jitter generation specification applies only to ONU. + +An ONU shall not generate a peak to peak jitter more than 0.2 unit interval (UI) at bit rates of 155.52 Mbit/s or 622.08 Mbit/s, and not more than 0.33 UI peak to peak at 1 244.16 Mbit/s, with no jitter applied to the downstream input and with a measurement bandwidth as specified in Table 2d to g-1. The maximum peak-to-peak jitter allowed at 2 488.32 Mbit/s and the related measurement frequency range is for further study. + +#### **8.2.8.10 Consecutive identical digit immunity** + +The OLT and the ONU shall have a consecutive identical digit (CID) immunity as specified in Table 2b to g. + +#### **8.2.8.11 Tolerance to reflected power** + +See clause 8.2.8.9 of [ITU-T G.983.1]. + +#### **8.2.8.12 Transmission quality and error performance** + +See clause 8.2.8.10 of [ITU-T G.983.1]. + +**Table 2a – Physical medium dependent layer parameters of ODN** + +| Items | Unit | Specification | +|---------------------------------------------------------------------------------------------------------------------------------------------|------|--------------------------------------------------------------------------------| +| Fibre type (Note 1) | – | [ITU-T G.652] | +| Attenuation range [ITU-T G.982] | dB | Class A: 5-20
Class B: 10-25
Class C: 15-30 | +| Differential optical path loss | dB | 15 | +| Maximum optical path penalty | dB | 1 (see Note 5 in Table 2e and f-1) | +| Maximum logical reach | km | 60 (Note 2) | +| Maximum differential logical reach | km | 20 | +| Maximum fibre distance between send/receive (S/R) and receive/send (R/S) points | km | 20 (10 as option) | +| Minimum supported split ratio | – | Restricted by path loss
PON with passive splitters (16, 32 or 64 way split) | +| Bidirectional transmission | – | 1-fibre WDM or 2-fibre | +| Maintenance wavelength | nm | to be defined | +| NOTE 1 – For future extended reach (> 20 km), the use of different types of fibre is for further study, for a future PMD specification. | | | +| NOTE 2 – This is the maximum distance managed by the higher layers of the system (MAC, TC, Ranging), in view of a future PMD specification. | | | + +**Table 2b – Optical interface parameters of 1 244 Mbit/s downstream direction** + +| Items | Unit | Single fibre | | | Dual fibre | | | +|-------------------------------------------------------------------------------------------------|--------|---------------|----|----|---------------|----|----| +| OLT transmitter (optical interface O ld ) | | | | | | | | +| Nominal bit rate | Mbit/s | 1 244.16 | | | 1 244.16 | | | +| Operating wavelength | nm | 1 480-1 500 | | | 1 260-1 360 | | | +| Line code | – | Scrambled NRZ | | | Scrambled NRZ | | | +| Mask of the transmitter eye diagram | – | Figure 2 | | | Figure 2 | | | +| Maximum reflectance of equipment, measured at transmitter wavelength | dB | NA | | | NA | | | +| Minimum optical return loss (ORL) of ODN at O lu and O ld (Notes 1 and 2) | dB | more than 32 | | | more than 32 | | | +| ODN Class | | A | B | C | A | B | C | +| Mean launched power MIN | dBm | –4 | +1 | +5 | –4 | +1 | +5 | +| Mean launched power MAX | dBm | +1 | +6 | +9 | +1 | +6 | +9 | +| Launched optical power without input to the transmitter | dBm | NA | | | NA | | | +| Extinction ratio | dB | more than 10 | | | more than 10 | | | +| Tolerance to the transmitter incident light power | dB | more than –15 | | | more than –15 | | | + +**Table 2b – Optical interface parameters of 1 244 Mbit/s downstream direction** + +| Items | Unit | Single fibre | | | Dual fibre | | | +|-------------------------------------------------------------------------------|------|-----------------------------|-----|----------------|-----------------------------|-----|-----| +| If multi-longitudinal mode (MLM) laser – Maximum root mean square (RMS) width | nm | NA | | | NA | | | +| If single-longitudinal mode (SLM) laser – Maximum –20 dB width (Note 3) | nm | 1 | | | 1 | | | +| If SLM laser – Minimum side mode suppression ratio | dB | 30 | | | 30 | | | +| ONU receiver (optical interface O rd ) | | | | | | | | +| Maximum reflectance of equipment, measured at receiver wavelength | dB | less than –20 | | | less than –20 | | | +| Bit error ratio | – | less than 10 –10 | | | less than 10 –10 | | | +| ODN Class | | A | B | C | A | B | C | +| Minimum sensitivity | dBm | –25 | –25 | –26 | –25 | –25 | –25 | +| Minimum overload | dBm | –4 | –4 | –4
(Note 4) | –4 | –4 | –4 | +| Consecutive identical digit immunity | bit | more than 72 | | | more than 72 | | | +| Jitter tolerance | – | Figure 5 | | | Figure 5 | | | +| Tolerance to the reflected optical power | dB | less than 10 | | | less than 10 | | | + +NOTE 1 – The value of "minimum ORL of ODN at point Oru and Ord, and Olu and Old" should be more than 20 dB in optional cases that are described in Appendix I of [ITU-T G.983.1]. + +NOTE 2 – The values of ONU transmitter reflectance if the value of "minimum ORL of ODN at point Oru and Ord, and Olu and Old" is 20 dB are described in Appendix II of [ITU-T G.983.1]. + +NOTE 3 – Values of maximum –20 dB width, and minimum side mode suppression ratio are referred to in [b-ITU-T G.957]. + +NOTE 4 – While only –6 dBm overload is required to support the class C ODN, a –4 dBm overload value has been chosen here for ONU receiver uniformity across all ODN classes. + +**Table 2c – Optical interface parameters of 2 488 Mbit/s downstream direction** + +| Items | Unit | Single fibre | | | Dual fibre | | | +|---------------------------------------------------------------------------|--------|---------------|---|---|---------------|---|---| +| OLT transmitter (optical interface O ld ) | | | | | | | | +| Nominal bit rate | Mbit/s | 2 488.32 | | | 2 488.32 | | | +| Operating wavelength | nm | 1 480-1 500 | | | 1 260-1 360 | | | +| Line code | – | Scrambled NRZ | | | Scrambled NRZ | | | +| Mask of the transmitter eye diagram | – | Figure 2 | | | Figure 2 | | | +| Maximum reflectance of equipment, measured at transmitter wavelength | dB | NA | | | NA | | | +| Minimum ORL of ODN at O lu and O ld (Notes 1 and 2) | dB | more than 32 | | | more than 32 | | | +| ODN Class | | A | B | C | A | B | C | + +**Table 2c – Optical interface parameters of 2 488 Mbit/s downstream direction** + +| Items | Unit | Single fibre | | | Dual fibre | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------------|-----|-----------------|----------------------|-----|-----------------|--|--|--|--|--|--| +| | | 0 | +5 | +3
(Note 4) | 0 | +5 | +3
(Note 4) | | | | | | | +| Mean launched power MAX | dBm | +4 | +9 | +7
(Note 4) | +4 | +9 | +7
(Note 4) | | | | | | | +| Launched optical power without input to the transmitter | dBm | NA | | | NA | | | | | | | | | +| Extinction ratio (Note 5) | dB | more than 8.2 | | | more than 8.2 | | | | | | | | | +| Tolerance to the transmitter incident light power | dB | more than –15 | | | more than –15 | | | | | | | | | +| If MLM laser – Maximum RMS width | nm | NA | | | NA | | | | | | | | | +| If SLM laser – Maximum –20 dB width (Note 3) | nm | 1 | | | 1 | | | | | | | | | +| If SLM laser – Minimum side mode suppression ratio | dB | 30 | | | 30 | | | | | | | | | +| ONU receiver (optical interface O rd ) | | | | | | | | | | | | | | +| Maximum reflectance of equipment, measured at receiver wavelength | dB | less than –20 | | | less than –20 | | | | | | | | | +| Bit error ratio | – | less than $10^{-10}$ | | | less than $10^{-10}$ | | | | | | | | | +| ODN Class | | A | B | C | A | B | C | | | | | | | +| Minimum sensitivity | dBm | –21 | –21 | –28
(Note 4) | –21 | –21 | –28
(Note 4) | | | | | | | +| Minimum overload | dBm | –1 | –1 | –8
(Note 4) | –1 | –1 | –8
(Note 4) | | | | | | | +| Consecutive identical digit immunity | bit | more than 72 | | | more than 72 | | | | | | | | | +| Jitter tolerance | – | Figure 5 | | | Figure 5 | | | | | | | | | +| Tolerance to the reflected optical power | dB | less than 10 | | | less than 10 | | | | | | | | | +| NOTE 1 – The value of "minimum ORL of ODN at point O ru and O rd , and O lu and O ld " should be more than 20 dB in optional cases which are described in Appendix I of [ITU-T G.983.1]. | | | | | | | | | | | | | | +| NOTE 2 – The values of ONU transmitter reflectance if the value of "minimum ORL of ODN at point O ru and O rd , and O lu and O ld " is 20 dB are described in Appendix II of [ITU-T G.983.1]. | | | | | | | | | | | | | | +| NOTE 3 – Values of maximum –20 dB width, and minimum side mode suppression ratio are referred to in [b-ITU-T G.957]. | | | | | | | | | | | | | | +| NOTE 4 – These values assume the use of a high-power distributed feedback (DFB) laser for the OLT transmitter and of a receiver based on an avalanche photodiode (APD) for the ONU. Taking future developments of semiconductor optical amplifier (SOA) technology into account, a future alternative implementation could use a DFB laser + SOA or a higher power laser diode for the OLT transmitter, allowing a receiver based on a photodiode without internal avalanche (PIN) for the ONU. The assumed values would then be conditional on eye-safety regulations and practice:
Mean launched power MAX OLT transmitter: +12 dBm
Mean launched power MIN OLT transmitter: +8 dBm
Minimum sensitivity ONU receiver: –23 dBm
Minimum overload ONU receiver: –3 dBm | | | | | | | | | | | | | | +| NOTE 5 – The extinction ratio of 8.2 dB was a relaxation of the former value of 10 dB. The new value does imply an improvement in the ONU receiver of 0.5 dB optical modulation amplitude. | | | | | | | | | | | | | | + +**Table 2d – Optical interface parameters of 155 Mbit/s upstream direction** + +| Items | Unit | Single fibre | | | Dual fibre | | | +|---------------------------------------------------------------------------|-----------------------|-------------------------------|-----|-----|-------------------------------|-----|-----| +| ONU transmitter (optical interface Oru) | | | | | | | | +| Nominal bit rate | Mbit/s | 155.52 | | | 155.52 | | | +| Operating wavelength | nm | 1 260-1 360 | | | 1 260-1 360 | | | +| Line code | – | Scrambled NRZ | | | Scrambled NRZ | | | +| Mask of the transmitter eye diagram | – | Figure 3 | | | Figure 3 | | | +| Maximum reflectance of equipment, measured at transmitter wavelength | dB | less than –6 | | | less than –6 | | | +| Minimum ORL of ODN at O ru and O rd (Notes 1 and 2) | dB | more than 32 | | | more than 32 | | | +| ODN Class | | A | B | C | A | B | C | +| Mean launched power MIN | dBm | –6 | –4 | –2 | –6 | –4 | –2 | +| Mean launched power MAX | dBm | –0 | +2 | +4 | –1 | +1 | +3 | +| Launched optical power without input to the transmitter | dBm | less than Min sensitivity –10 | | | less than Min sensitivity –10 | | | +| Maximum Tx enable (Note 3) | bits | 2 | | | 2 | | | +| Maximum Tx disable (Note 3) | bits | 2 | | | 2 | | | +| Extinction ratio | dB | more than 10 | | | more than 10 | | | +| Tolerance to the transmitter incident light power | dB | more than –15 | | | more than –15 | | | +| If MLM laser – Maximum RMS width | nm | 5.8 | | | 5.8 | | | +| If SLM laser – Maximum –20 dB width (Note 4) | nm | 1 | | | 1 | | | +| If SLM laser – Minimum side mode suppression ratio | dB | 30 | | | 30 | | | +| Jitter transfer | – | Figure 4 | | | Figure 4 | | | +| Jitter generation from 0.5 kHz to 1.3 MHz | UI peak to peak (p-p) | 0.2 | | | 0.2 | | | +| OLT receiver (optical interface Olu) | | | | | | | | +| Maximum reflectance of equipment, measured at receiver wavelength | dB | less than –20 | | | less than –20 | | | +| Bit error ratio | – | less than $10^{-10}$ | | | less than $10^{-10}$ | | | +| ODN Class | | A | B | C | A | B | C | +| Minimum sensitivity | dBm | –27 | –30 | –33 | –27 | –30 | –33 | +| Minimum overload | dBm | –5 | –8 | –11 | –6 | –9 | –12 | + +**Table 2d – Optical interface parameters of 155 Mbit/s upstream direction** + +| Items | Unit | Single fibre | Dual fibre | +|--------------------------------------|------|--------------|--------------| +| Consecutive identical digit immunity | bit | more than 72 | more than 72 | +| Jitter tolerance | – | NA | NA | +| Tolerance to reflected optical power | dB | less than 10 | less than 10 | + +NOTE 1 – The value of "minimum ORL of ODN at point Oru and Ord, and Olu and Old" should be more than 20 dB in optional cases which are described in Appendix I of [ITU-T G.983.1]. + +NOTE 2 – The values of ONU transmitter reflectance if the value of "minimum ORL of ODN at point Oru and Ord, and Olu and Old" is 20 dB are described in Appendix II of [ITU-T G.983.1]. + +NOTE 3 – As defined in clause 8.2.6.3.1. + +NOTE 4 – Values of maximum –20 dB width, and minimum side mode suppression ratio are referred to in [b-ITU-T G.957]. + +**Table 2e – Optical interface parameters of 622 Mbit/s upstream direction** + +| Items | Unit | Single fibre | | | Dual fibre | | | +|---------------------------------------------------------------------------|--------|--------------------------------------------------------------------------------------|---|---|--------------------------------------------------------------------------------------|---|---| +| ONU transmitter (optical interface Oru) | | | | | | | | +| Nominal bit rate | Mbit/s | 622.08 | | | 622.08 | | | +| Operating wavelength (Note 5) | nm | MLM type 1 or SLM: 1 260~1 360
MLM type 2: 1 280~1 350
MLM type 3: 1 288~1 338 | | | MLM type 1 or SLM: 1 260~1 360
MLM type 2: 1 280~1 350
MLM type 3: 1 288~1 338 | | | +| Line code | – | Scrambled NRZ | | | Scrambled NRZ | | | +| Mask of the transmitter eye diagram | – | Figure 3 | | | Figure 3 | | | +| Maximum reflectance of equipment, measured at transmitter wavelength | dB | less than –6 | | | less than –6 | | | +| Minimum ORL of ODN at O ru and O rd (Notes 1 and 2) | dB | more than 32 | | | more than 32 | | | +| ODN Class | | A | B | C | A | B | C | +| Mean launched power MIN | dBm | –6 | | | –1 | | | +| Mean launched power MAX | dBm | –1 | | | +4 | | | +| Launched optical power without input to the transmitter | dBm | less than Min sensitivity –10 | | | less than Min sensitivity –10 | | | +| Maximum Tx enable (Note 3) | bits | 8 | | | 8 | | | +| Maximum Tx disable (Note 3) | bits | 8 | | | 8 | | | +| Extinction ratio | dB | more than 10 | | | more than 10 | | | +| Tolerance to transmitter incident light power | dB | more than –15 | | | more than –15 | | | +| MLM laser – Maximum RMS width (Note 5) | nm | MLM type 1: 1.4
MLM type 2: 2.1
MLM type 3: 2.7 | | | MLM type 1: 1.4
MLM type 2: 2.1
MLM type 3: 2.7 | | | + +**Table 2e – Optical interface parameters of 622 Mbit/s upstream direction** + +| Items | Unit | Single fibre | | | Dual fibre | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------|-----|-----|----------------------|-----|-----|--|--|--|--|--|--| +| SLM Laser – Maximum –20 dB width (Note 4) | nm | 1 | | | 1 | | | | | | | | | +| If SLM Laser – Minimum side mode suppression ratio | dB | 30 | | | 30 | | | | | | | | | +| Jitter transfer | – | Figure 4 | | | Figure 4 | | | | | | | | | +| Jitter generation from 2.0 kHz to 5.0 MHz | UI p-p | 0.2 | | | 0.2 | | | | | | | | | +| OLT receiver (optical interface Olu) | | | | | | | | | | | | | | +| Maximum reflectance of equipment, measured at receiver wavelength | dB | less than –20 | | | less than –20 | | | | | | | | | +| Bit error ratio | – | less than $10^{-10}$ | | | less than $10^{-10}$ | | | | | | | | | +| ODN Class | | A | B | C | A | B | C | | | | | | | +| Minimum sensitivity | dBm | –27 | –27 | –32 | –27 | –27 | –32 | | | | | | | +| Minimum overload | dBm | –6 | –6 | –11 | –6 | –6 | –11 | | | | | | | +| Consecutive identical digit immunity | bit | more than 72 | | | more than 72 | | | | | | | | | +| Jitter tolerance | – | NA | | | NA | | | | | | | | | +| Tolerance to the reflected optical power | dB | less than 10 | | | less than 10 | | | | | | | | | +| NOTE 1 – The value of "minimum ORL of ODN at point O ru and O rd , and O lu and O ld " should be more than 20 dB in optional cases which are described in Appendix I of [ITU-T G.983.1]. | | | | | | | | | | | | | | +| NOTE 2 – The values of ONU transmitter reflectance if the value of "minimum ORL of ODN at point O ru and O rd , and O lu and O ld " is 20 dB are described in Appendix II of [ITU-T G.983.1]. | | | | | | | | | | | | | | +| NOTE 3 – As defined in clause 8.2.6.3.1. | | | | | | | | | | | | | | +| NOTE 4 – Values of maximum –20 dB width, and minimum side mode suppression ratio are referred to in [b-ITU-T G.957]. | | | | | | | | | | | | | | +| NOTE 5 – Transmitter types meeting narrower spectral width specifications are allowed wider central wavelength ranges. The specified laser types produce less than 1 dB of optical path penalty over the ODN. Lasers with different optical parameters may be substituted provided that: 1) the total wavelength range does not exceed 1 260~1 360 nm, and 2) any increase in optical path penalty over 1 dB is compensated by an increase of the minimum transmitted launch power or an increase of the minimum receiver sensitivity. | | | | | | | | | | | | | | + +**Table 2f-1 – Optical interface parameters of 1 244 Mbit/s upstream direction** + +| Items | Unit | Single fibre | | | Dual fibre | | | +|---------------------------------------------------------------------------|--------|----------------------------------|-----|-----|----------------------------------|-----|-----| +| ONU transmitter (optical interface Oru) | | | | | | | | +| Nominal bit rate | Mbit/s | 1 244.16 | | | 1 244.16 | | | +| Operating wavelength | nm | 1 260-1 360 | | | 1 260-1 360 | | | +| Line code | – | Scrambled NRZ | | | Scrambled NRZ | | | +| Mask of the transmitter eye diagram | – | Figure 3 | | | Figure 3 | | | +| Maximum reflectance of equipment, measured at transmitter wavelength | dB | less than –6 | | | less than –6 | | | +| Minimum ORL of ODN at O ru and O rd (Notes 1 and 2) | dB | more than 32 | | | more than 32 | | | +| ODN Class | | A | B | C | A | B | C | +| Mean launched power MIN | dBm | –3
(Note 5) | –2 | +2 | –3
(Note 5) | –2 | +2 | +| Mean launched power MAX | dBm | +2
(Note 5) | +3 | +7 | +2
(Note 5) | +3 | +7 | +| Launched optical power without input to the transmitter | dBm | less than Min sensitivity
–10 | | | less than Min sensitivity
–10 | | | +| Maximum Tx enable (Note 3) | bits | 16 | | | 16 | | | +| Maximum Tx disable (Note 3) | bits | 16 | | | 16 | | | +| Extinction ratio | dB | more than 10 | | | more than 10 | | | +| Tolerance to transmitter incident light power | dB | more than –15 | | | more than –15 | | | +| MLM laser – Maximum RMS width | nm | (Note 5) | | | (Note 5) | | | +| SLM Laser – Maximum –20 dB width (Note 4) | nm | 1 | | | 1 | | | +| If SLM Laser – Minimum side mode suppression ratio | dB | 30 | | | 30 | | | +| Jitter transfer | – | Figure 4 | | | Figure 4 | | | +| Jitter generation from 4.0 kHz to 10.0 MHz | UI p-p | 0.33 | | | 0.33 | | | +| OLT receiver (optical interface Olu) | | | | | | | | +| Maximum reflectance of equipment, measured at receiver wavelength | dB | less than –20 | | | less than –20 | | | +| Bit error ratio | – | less than 10 –10 | | | less than 10 –10 | | | +| ODN Class | | A | B | C | A | B | C | +| Minimum sensitivity | dBm | –24
(Note 6) | –28 | –29 | –24
(Note 6) | –28 | –29 | +| Minimum overload | dBm | –3
(Note 6) | –7 | –8 | –3
(Note 6) | –7 | –8 | + +**Table 2f-1 – Optical interface parameters of 1 244 Mbit/s upstream direction** + +| Items | Unit | Single fibre | Dual fibre | +|------------------------------------------|------|--------------|--------------| +| Consecutive identical digit immunity | Bit | more than 72 | More than 72 | +| Jitter tolerance | – | NA | NA | +| Tolerance to the reflected optical power | dB | less than 10 | less than 10 | + +NOTE 1 – The value of "minimum ORL of ODN at point Oru and Ord, and Olu and Old" should be more than 20 dB in optional cases which are described in Appendix I of [ITU-T G.983.1]. + +NOTE 2 – The values of ONU transmitter reflectance if the value of "minimum ORL of ODN at point Oru and Ord, and Olu and Old" is 20 dB are described in Appendix II of [ITU-T G.983.1]. + +NOTE 3 – As defined in clause 8.2.6.3.1. + +NOTE 4 – Values of maximum –20 dB width, and minimum side mode suppression ratio are referred to in [b-ITU-T G.957]. + +NOTE 5 – While MLM laser types are not applicable to support the full ODN fibre distance of Table 2a, such lasers can be used if the maximum ODN fibre distance between R/S and S/R is restricted to 10 km. The MLM laser types of Table 2e can be employed to support this restricted fibre distance at 1 244.16 Mbit/s. These laser types are subject to the same conditions as indicated in Note 5 of Table 2e. + +NOTE 6 – These values assume the use of a PIN-based receiver at the OLT for Class A. Depending on the number of ONUs connected to the OLT, an alternative implementation from a cost point of view could be based on an APD-based receiver at the OLT, allowing it to use more economical lasers with lower fibre-coupled emitted power at the ONUs. In this case, the values for class A would be: + +Mean launched power MIN ONU transmitter: –7 dBm + +Mean launched power MAX ONU transmitter: –2 dBm + +Minimum sensitivity OLT receiver: –28 dBm + +Minimum overload OLT receiver: –7 dBm + +**Table 2f-2 – Optical interface parameters of 1 244 Mbit/s upstream direction, +using power levelling mechanism at ONU transmitter** + +| Items | Unit | Single fibre | | | Dual fibre | | | +|-----------------------------------------------------------|------|-----------------|-----|-----|-----------------|-----|-----| +| ONU transmitter (optical interface Oru) | | | | | | | | +| ODN Class | | A | B | C | A | B | C | +| Mean launched power MIN | dBm | -2
(Note 2) | -2 | +2 | -2
(Note 2) | -2 | +2 | +| Mean launched power MAX | dBm | +3
(Note 2) | +3 | +7 | +3
(Note 2) | +3 | +7 | +| OLT receiver (optical interface Olu) | | | | | | | | +| ODN Class | | A | B | C | A | B | C | +| Minimum sensitivity | dBm | -23
(Note 2) | -28 | -29 | -23
(Note 2) | -28 | -29 | +| Minimum overload | dBm | -8
(Note 2) | -13 | -14 | -8
(Note 2) | -13 | -14 | + +NOTE 1– This table only indicates the parameters of Table 2f-1 that change due to the application of the power levelling mechanism at ONU transmitter, namely the launched powers of the ONU transmitter and the sensitivity and overload of the OLT receiver. All other parameters and notes are identical to those in Table 2f-1. + +NOTE 2 – These values assume the use of a PIN-based receiver at the OLT for Class A. Depending on the number of ONUs connected to the OLT, an alternative implementation from a cost point of view could be based on an APD-based receiver at the OLT, allowing it to use more economical lasers with lower fibre-coupled emitted power at the ONUs. In this case, the values for class A would be: + +Mean launched power MIN ONU transmitter: -7 dBm + +Mean launched power MAX ONU transmitter: -2 dBm + +Minimum sensitivity OLT receiver: -28 dBm + +Minimum overload OLT receiver: -10 dBm + +The impact of power levelling is less, due to the restriction on the minimal power to be emitted to guarantee the eye-diagram. + +**Table 2g-1 – Optical interface parameters of 2 488 Mbit/s upstream direction** + +| Items | Unit | Single fibre | | | Dual fibre | | | | | | | | | +|----------------------------------------------------------------------|--------|---------------|-----|-----|---------------|-----|-----|--|--|--|--|--|--| +| ONU transmitter (optical interface Oru) | | | | | | | | | | | | | | +| Nominal bit rate | Mbit/s | 2 488.32 | | | 2 488.32 | | | | | | | | | +| Operating wavelength | nm | 1 260-1 360 | | | 1 260-1 360 | | | | | | | | | +| Line code | – | Scrambled NRZ | | | Scrambled NRZ | | | | | | | | | +| Mask of the transmitter eye diagram | – | Figure 3 | | | Figure 3 | | | | | | | | | +| Maximum reflectance of equipment, measured at transmitter wavelength | dB | FFS | | | FFS | | | | | | | | | +| Minimum ORL of ODN at O ru and O rd | dB | FFS | | | FFS | | | | | | | | | +| ODN Class | | A | B | C | A | B | C | | | | | | | +| Mean launched power MIN | dBm | FFS | FFS | FFS | FFS | FFS | FFS | | | | | | | +| Mean launched power MAX | dBm | FFS | FFS | FFS | FFS | FFS | FFS | | | | | | | +| Launched optical power without input to the transmitter | dBm | FFS | | | FFS | | | | | | | | | +| Maximum Tx enable (Note 2) | bits | 32 | | | 32 | | | | | | | | | +| Maximum Tx disable (Note 2) | bits | 32 | | | 32 | | | | | | | | | +| Extinction ratio | dB | FFS | | | FFS | | | | | | | | | +| Tolerance to the transmitter incident light power | dB | FFS | | | FFS | | | | | | | | | +| If MLM laser – Maximum RMS width | nm | FFS | | | FFS | | | | | | | | | +| If SLM laser – Maximum –20 dB width | nm | FFS | | | FFS | | | | | | | | | +| If SLM Laser – Minimum side mode suppression ratio | dB | FFS | | | FFS | | | | | | | | | +| Jitter transfer | – | Figure 4 | | | Figure 4 | | | | | | | | | +| Jitter generation (measurement frequency range is FFS) | UI p-p | FFS | | | FFS | | | | | | | | | +| OLT receiver (optical interface Olu) | | | | | | | | | | | | | | +| Maximum reflectance of equipment, measured at receiver wavelength | dB | FFS | | | FFS | | | | | | | | | +| Bit error ratio | – | FFS | | | FFS | | | | | | | | | +| ODN Class | | A | B | C | A | B | C | | | | | | | +| Minimum sensitivity | dBm | FFS | FFS | FFS | FFS | FFS | FFS | | | | | | | +| Minimum overload | dBm | FFS | FFS | FFS | FFS | FFS | FFS | | | | | | | +| Consecutive identical digit immunity | Bit | FFS | | | FFS | | | | | | | | | +| Jitter tolerance | – | FFS | | | FFS | | | | | | | | | +| Tolerance to the reflected optical power | dB | FFS | | | FFS | | | | | | | | | +| NOTE 1 – FFS: for further study. | | | | | | | | | | | | | | +| NOTE 2 – As defined in clause 8.2.6.3.1. | | | | | | | | | | | | | | + +**Table 2g-2 – Optical interface parameters of 2 488 Mbit/s +upstream direction, using power levelling mechanism at ONU transmitter** + +| Items | Unit | Single fibre | | | Dual fibre | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------------|-----|-----|------------|-----|-----| +| ONU transmitter (optical interface Oru) | | | | | | | | +| ODN Class | | A | B | C | A | B | C | +| Mean launched power MIN | dBm | FFS | FFS | FFS | FFS | FFS | FFS | +| Mean launched power MAX | dBm | FFS | FFS | FFS | FFS | FFS | FFS | +| OLT receiver (optical interface Olu) | | | | | | | | +| ODN Class | | A | B | C | A | B | C | +| Minimum sensitivity | dBm | FFS | FFS | FFS | FFS | FFS | FFS | +| Minimum overload | dBm | FFS | FFS | FFS | FFS | FFS | FFS | +| NOTE – This table only indicates the parameters of Table 2g-1 that change due to the application of the power levelling mechanism at the ONU transmitter, namely the launched powers of the ONU transmitter and the sensitivity and overload of the OLT receiver. All other parameters and notes are identical to those of Table 2g-1. | | | | | | | | + + + +Eye diagram mask showing Amplitude vs. Time (0 to 1 UI). The vertical axis (Amplitude) has markers at -y1, 0, y1, 0.5, y2, 1, and 1+y1. The horizontal axis (Time) has markers at 0, x1, x2, x3, x4, and 1. The mask defines a region for the eye opening, with boundaries at x1, x2, x3, and x4, and amplitude levels y1, y2, and 1+y1. + +| | 1244.16 Mbit/s | 2488.32 Mbit/s | +|---------|----------------|----------------| +| x1/x4 | 0.28/0.72 | --- | +| x2/x3 | 0.40/0.60 | --- | +| x3 – x2 | --- | 0.2 | +| y1/y2 | 0.20/0.80 | 0.25/0.75 | + + + +[Test set-up] + +Block diagram of the test set-up: Optical transmitter -> Attenuator\* -> O/E converter, fourth-order Thomson filter\*\* -> Waveform monitor. The label G.984.2\_F02 is present below the waveform monitor block. + +\* Attenuator is used if necessary. + +\*\* Cut-off frequency (3 dB attenuation frequency) of the filter is 0.75 times output nominal bit rate. + +NOTE – In the case of 2488.32 Mbit/s, x2 and x3 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. + +**Figure 2 – Mask of the eye diagram for the downstream transmission signal** + + + +Eye diagram mask showing signal levels (y1, y2, y3, y4, 1+y1, -y1) versus time (x1, x2, 0.5, x3, x4) over 1 UI. The diagram shows a shaded region representing the allowed signal area, with a central white region for the signal. The y-axis has labels 1+y1, 1, y4, y3, 0.5, y2, y1, 0, -y1. The x-axis has labels 0, x1, x2, 0.5, x3, x4, 1, with a bracket below indicating 1 UI. + +| | 155.52 Mbit/s | 622.08 Mbit/s | 1244.16 Mbit/s | 2488.32 Mbit/s | +|-------|---------------|---------------|----------------|-------------------| +| x1/x4 | 0.10/0.90 | 0.20/0.80 | 0.22/0.78 | For further study | +| x2/x3 | 0.35/0.65 | 0.40/0.60 | 0.40/0.60 | For further study | +| y1/y4 | 0.13/0.87 | 0.15/0.85 | 0.17/0.83 | For further study | +| y2/y3 | 0.20/0.80 | 0.20/0.80 | 0.20/0.80 | For further study | + + + +Block diagram of the test setup: Optical transmitter -> Attenuator\* -> O/E converter, fourth-order Thomson filter\*\* -> Waveform monitor. The text G.984.2\_F03 is at the bottom right. + +\* Attenuator is used if necessary. + +\*\* Cut-off frequency (3 dB attenuation frequency) of the filter is 0.75 times output nominal bit rate. + +**Figure 3 – Mask of the eye diagram for the upstream transmission signal** + +![Graph of Jitter gain [dB] versus Frequency. The gain is constant at P [dB] until the cut-off frequency fc, after which it decreases with a slope of -20 dB/dec. The text G.984.2_F04 is at the bottom right.](114a0f7c7ac69ab82f03d68650cf8e88_img.jpg) + +Graph of Jitter gain [dB] versus Frequency. The gain is constant at P [dB] until the cut-off frequency fc, after which it decreases with a slope of -20 dB/dec. The text G.984.2\_F04 is at the bottom right. + +| Downstream bit rate (Mbit/s) | fc [kHz] | P [dB] | +|------------------------------|----------|--------| +| 1244.16 | 1000 | 0.1 | +| 2488.32 | 2000 | 0.1 | + +G.984.2\_F04 + +**Figure 4 – Jitter transfer for ONU** + +![Figure 5: Jitter tolerance mask for ONU. The top part is a graph of Input jitter amplitude (A1, A2) vs Frequency (f0, ft) with a slope of -20 dB/dec. The bottom part is a table with 5 columns: Downstream bit rate (Mbit/s), ft [kHz], f0 [kHz], A1 [UIp-p], A2 [UIp-p].](4cec89a753c447a050c0171c274f2acb_img.jpg) + +| Downstream bit rate (Mbit/s) | ft [kHz] | f0 [kHz] | A1 [UIp-p] | A2 [UIp-p] | +|------------------------------|----------|----------|------------|------------| +| 1244.16 | 500 | 50 | 0.075 | 0.75 | +| 2488.32 | 1000 | 100 | 0.075 | 0.75 | + +G.984.2\_F05 + +Figure 5: Jitter tolerance mask for ONU. The top part is a graph of Input jitter amplitude (A1, A2) vs Frequency (f0, ft) with a slope of -20 dB/dec. The bottom part is a table with 5 columns: Downstream bit rate (Mbit/s), ft [kHz], f0 [kHz], A1 [UIp-p], A2 [UIp-p]. + +**Figure 5 – Jitter tolerance mask for ONU** + +## 8.3 Interaction between GPON PMD layer and TC layer + +As previously stated, this Recommendation describes characteristics of the PMD layer of an OAN with the capability of transporting various services between the user network interface and the SNI. However, some GPON functionalities belong to or have impact on both the PMD layer and TC layer. Clauses 8.3.1 to 8.3.3 describe those functionalities and explain the relation between the GPON PMD layer and TC layer. The latter is specified in [ITU-T G.984.3]. + +### 8.3.1 Forward error correction + +Systems employing forward error correction (FEC) will be able to support the ODN attenuation ranges of Table 2a with lower performance transmitters and receivers than indicated in Table 2b to g-2. + +The effective optical gain $G$ of systems employing FEC is defined as the difference of optical power at the receiver input, with and without FEC, for a BER of $1 \times 10^{-10}$ . + + + +G.984.2\_F06 + +Figure 6: Effective optical gain G achieved with FEC. The graph shows BER vs Popt. A dashed curve (without FEC) and a solid curve (with FEC) are shown. A horizontal line at BER = 1 x 10^-10 intersects both curves. The horizontal distance between the intersection points is labeled G. + +**Figure 6 – Effective optical gain $G$ achieved with FEC** + +In systems employing FEC with an effective optical gain, $G$ , expressed in decibels, either of the two following performance variations from Table 2 are acceptable (but not both, to facilitate interoperability): + +- i) minimum and maximum transmitter power may be reduced by $G$ ; or +- ii) minimum receiver sensitivity may be decreased by $G$ . + +Alternatively, while maintaining the same performance of transmitters and receivers indicated in Table 2b to g-2, the effective optical coding gain $G$ can be used to achieve a longer physical reach or a higher split ratio when using an MLM laser in the ONU. In this case, FEC is used to reduce the penalty due to MPN. + +FEC is implemented at the TC layer, therefore, it is not described in this Recommendation. + +The receiver overload specification is not altered by FEC gain. + +### 8.3.2 Power levelling mechanism at ONU transmitter + +The OLT receiver requirements dictate the use of APD-based implementations at 1 244.16 Mbit/s and above. Such receivers must provide both a high sensitivity and a large dynamic range for a burst-mode reception at high bit rates. This imposes a compromise for the multiplication factor $M$ of the APD-based receiver, which is not straightforward, particularly for GPON supporting the enhancement band where the requirements rise further due to the losses and loss variations of the extra WDM components. + +In order to relax the dynamic range of the OLT receiver, the transmitter power level of the ONUs experiencing a low ODN loss should be reduced in order to avoid overload of the OLT receiver. For this reason, a suitable power levelling mechanism has to be implemented. + +The power levelling mechanism requires functionalities belonging to the TC layer, such as the ONU capability to increase/reduce the transmitted power on the basis of downstream messages sent by the OLT. Such functionalities, as well as the capability to perform power levelling during initialization or also during operation, are not described in this Recommendation. + +The requirements at the PMD layer to allow a suitable power levelling mechanism for GPON systems are reported in the following. The background for the requirements is described in Appendix II. + +- a) The ONU output power can have three modes. The PMD can be locally directed to operate in any mode. Upon such a control input, the PMD will perform whatever actions it needs to take in order to achieve an output power that lies within the range specified in the following: + +Mode 0: Normal (mean launched MIN/MAX as stated in Table 2f-2 and g-2) + +Mode 1: Low 1 = Normal – 3 dB + +Mode 2: Low 2 = Normal – 6dB + +- b) The OLT measures the average optical power, $P$ , of each ONU burst. The OLT compares this measurement to one or two thresholds (TL (threshold low) and TH (threshold high)), and issues one of three indications as shown: + +$P > TH$ : power\_high indication + +$P < TL$ : power\_low indication + +$TL < P < TH$ : power\_ok indication + +NOTE – TL is required (single threshold operation), TH is an optional requirement (double threshold operation). + +The uncertainty range on the threshold comparison must be maximum 4 dB. + +- c) Taking into account the values of the optical power corresponding to the OLT receiver (Rx) minimum sensitivity $P_{ms}$ and minimum overload $P_{mo}$ stated in Table 2f-2 and g-2, the values of TH and TL must satisfy the following conditions: + +Double threshold operation: + +R1: $P_{mo} > TH > (P_{mo} - 4 \text{ dB})$ + +R2: $(P_{ms} + 5 \text{ dB}) > TL > (P_{ms} + 1 \text{ dB})$ + +R3: $TH - TL > 8 \text{ dB}$ . + +Single threshold operation: + +R2: $(P_{\text{ms}} + 7 \text{ dB}) > \text{TL} > (P_{\text{ms}} + 1 \text{ dB})$ . + +- d) The OLT Rx must be able to measure the burst power (but not reliably read the data) at sensitivity – 5 dB (see Table 2f-2 and g-2). + +The benefits of the power levelling mechanism are as follows. + +- Reduced dynamic range requirement at the OLT receiver, as an ONU at low ODN loss will be set at a low transmitter power. +- Increase of laser lifetime and reduction of power consumption when an ONU is working in low-power mode. + +The power levelling mechanism allows the relaxation of the requirements for the OLT receiver, as indicated in Table 2f-2 and g-2. + +### 8.3.3 Upstream physical layer overhead + +The GPON frame structure is described in [ITU-T G.984.3], devoted to the specification of the TC layer. However, the upstream bursts must be preceded by a suitable physical layer overhead, which is used to accommodate several physical processes in the GPON. Table 3 shows the length of the physical layer overhead for all the upstream bit rates specified in this Recommendation. + +**Table 3 – GPON upstream physical layer overhead** + +| Upstream bit rate
Mbit/s | Overhead bytes | +|------------------------------------|-----------------------| +| 155.52 | 4 | +| 622.08 | 8 | +| 1 244.16 | 12 | +| 2 488.32 | 24 | + +Moreover, Appendix I provides information on the physical processes that have to be performed during the physical layer overhead ( $T_{\text{plo}}$ ) time, and some guidelines for an optimized usage of such time. + +# Annex A + +## Industry best practice for 2.488 Gbit/s downstream, 1.244 Gbit/s upstream GPON class B+ + +(This annex forms an integral part of this Recommendation.) + +## A.1 Introduction + +The widespread interest in the 2.4 Gbit/s downstream, 1.2 Gbit/s upstream GPON system has provided increased visibility into the feasibility of loss budgets for this system. This annex describes industry best practices for this rate combination. + +The notable variations from the loss budgets found elsewhere in this Recommendation include: + +- overall loss budgets midway between class B and class C; +- different value of optical path penalties; +- the OLT must support FEC in the downstream. + +These variations can provide increased capabilities for operation of GPON systems. Therefore, the budgets contained in this annex are recommended over and above all others in this Recommendation for the 2.4/1.2 Gbit/s rate PON. This budget is named B+. + +## A.2 System applications + +There are currently two major applications for the GPON system. The first is a full-service system with a video overlay. The second is a digital-only system without a video overlay. These two applications are illustrated in Figure III.1. + + + +a) Video overlay + +b) Digital-only + +G.984.2(19)\_FA.1 + +Figure A.1 – GPON applications. The diagram shows two system configurations: a) Video overlay and b) Digital-only. Both show an OLT (2 wavelength) connected to an ODN via an S/R interface. In (a), a Video Tx is connected to the OLT, and the ODN is connected to an ONU (3 wavelength) via an R/S interface. In (b), the ODN is connected to an ONU (2 wavelength) via an R/S interface. A small note 'G.984.2(19)\_FA.1' is present in the bottom right of the diagram area. + +Figure A.1 – GPON applications + +## A.3 Optical specifications + +The optical specifications for the OLT and ONU optics are given in Table A.1, which refers to power levels measured at the interface points shown in Figure A.1, i.e., both types a (video overlay) and b (digital-only) systems. Specifically, any WDM filters external to the OLT or ONU equipment are considered part of the ODN. These specifications are meant to augment similar specifications found in Table 2. All other specifications found elsewhere in Table 2 still apply. + +The ONU sensitivity can be achieved either using an APD without FEC or a PIN with FEC. The choice is a matter of ONU implementation. The APD solution is seen as an immediately available option, while the PIN with FEC solution is a longer-term option that depends on the introduction of higher performance receiver circuitry. The OLT must support FEC in the downstream by having the + +capability of calculating and transmitting the FEC parity bytes in the downstream signal. The OLT equipment must also have the ability to activate or deactivate the downstream FEC feature by operations system command. The ONU can optionally support FEC decoding in the downstream, and in any specific instance the ONU can use the FEC parity at its own discretion. + +The optical penalty does not include any Raman impairment in the downstream wavelength. Any penalty due to this effect must be accounted for out of the link budget. However, any system with an appreciable Raman effect will also have a significant length of fibre. Because of the loss differential between 1 490 nm and 1 310 nm, it is anticipated that the Raman impairment will be compensated by the lower fibre loss at 1 490 nm. + +**Table A.1 – B+ Optical power levels for the 2.4 Gbit/s downstream, 1.2 Gbit/s upstream system** + +| Items | Unit | Single fibre | +|----------------------------|------|--------------| +| OLT: | | OLT | +| Mean launched power MIN | dBm | +1.5 | +| Mean launched power MAX | dBm | +5 | +| Minimum sensitivity | dBm | –28 | +| Minimum overload | dBm | –8 | +| Downstream optical penalty | dB | 0.5 | +| ONU: | | ONU | +| Mean launched power MIN | dBm | +0.5 | +| Mean launched power MAX | dBm | +5 | +| Minimum sensitivity | dBm | –27 | +| Minimum overload | dBm | –8 | +| Upstream optical penalty | dB | 0.5 | + +## A.4 Link budget + +The link budget is given in Table A.2. This budget covers all optical components between the OLT and ONU, including non-integrated WDM filters for the multiplex of video overlays and other enhancement band services, and must include any Raman impairment from the overlay signal. + +**Table A.2 – B+ loss budgets for the GPON system** + +| Items | Unit | Single fibre | +|----------------------------------|------|--------------| +| Minimum optical loss at 1 490 nm | dB | 13 | +| Minimum optical loss at 1 310 nm | dB | 13 | +| Maximum optical loss at 1 490 nm | dB | 28 | +| Maximum optical loss at 1 310 nm | dB | 28 | + +In comparison, the broadband passive optical network (BPON) class B+ budgets recommended in [ITU-T G.983.3] are shown in Table A.3. The GPON budget is similar to the video overlay system in that it supports a 13 dB minimum loss, and it is similar to the digital-only budget in that it is symmetric and it supports a 28 dB maximum loss. It is theoretically possible that a PON that complies with the BPON B+ budgets might not comply with the GPON budget; however, such cases should be very rare in the actual deployed base of PONs. Therefore, the GPON budget should be compatible with practically all deployed PONs. + +**Table A.3 – Loss budgets for the BPON [ITU-T G.983.3] systems** + +| Items | Unit | Single fibre | +|----------------------------------------|------|--------------| +| Video overlay system (OLT1-ONT) | | | +| Minimum optical loss at 1 490 nm | dB | 9 | +| Minimum optical loss at 1 310 nm | dB | 13 | +| Maximum optical loss at 1 490 nm | dB | 27 | +| Maximum optical loss at 1 310 nm | dB | 29 | +| Digital-only system (OLT2-ONT) | | | +| Minimum optical loss at 1 490 nm | dB | 10 | +| Minimum optical loss at 1 310 nm | dB | 10 | +| Maximum optical loss at 1 490 nm | dB | 28 | +| Maximum optical loss at 1 310 nm | dB | 28 | + +# Annex B + +## Description of physical layer measurements to support optical layer supervision + +(This annex forms an integral part of this Recommendation.) + +## B.1 Introduction + +This annex describes physical layer parameter measurements that are required to provide the GPON system with a basic optical layer supervision capability. The quantities to be measured are enumerated, along with the desired range, accuracy and resolution. These measurements can be obtained by different practical and cost-effective monitoring methods, and the method of measurement is left to implementation choice. + +## B.2 Transceiver parameters monitoring + +In PON systems, physical monitoring for OLS may be used for the following. + +- 1) Normal status monitoring: Get and buffer "historic" data as a reference in a normally working system. +- 2) Degradation detection: Find the potential faults before they become service-affecting, and identify the source of the problem (e.g., ODN, OLT or ONT). +- 3) Fault management: Detect, localize and diagnose faults. + +In order to achieve these objectives, the following performance items should be monitored in a PON system. + +- Transceiver temperature (OLT and ONT); +- Transceiver voltage (OLT and ONT); +- Laser bias current (OLT and ONT); +- OLT transmit power; +- OLT receive power (per ONT); +- ONT transmit power; +- ONT receive power. + +Clause B.3 specifies recommended measurement performance parameters for each of these transceiver performance measurements. + +NOTE – These are obtainable using currently available detection and monitoring technology. + +## B.3 Measurement table for transceiver parameters + +Table B.1 gives information on the standard measurement performance that should be obtainable with measurement equipment embedded in the OLT or ONTs. + +NOTE – The values specified in Table B.1 pertain to the measurement, and not the reporting, of data. Therefore, the resolution mainly refers to the intrinsic quantization size of the measurement circuit, and not the message field format of the report. The typical RT refers to the timeliness of the measurement circuit in the optical module, and not to the actual reporting of data over the PON or to the element management system (EMS). + +**Table B.1 – Optical line supervision-related measurement specifications** + +| | Typical range
[Note 1] | Resolution | Accuracy | Repeatability | Typical
response
time | +|----------------------------------------|---------------------------|-----------------|-----------------|---------------------|-----------------------------| +| Temperature – OLT and ONT | –45 to +90 C | 0.25 C | ±3 C | ±1 C | 1 s | +| Voltage – OLT and ONT
[Note 4] | 0 to 6.55 V | 0.5% of nominal | ±3% of nominal | ±1% of nominal | 1 s | +| Bias current – OLT and ONT
[Note 4] | 0 to 131 mA | 1% of nominal | ±10% of nominal | ±5% of nominal | 1 s | +| ONT transmit power | –10 to +8 dBm | 0.1 dB | ±3 dB | ±0.5 dB
[Note 2] | 300 ns | +| ONT receive power | –34 to –8 dBm | 0.1 dB | ±3 dB | ±0.5 dB
[Note 2] | 300 ns | +| OLT transmit power | –10 to +9 dBm | 0.1 dB | ±2 dB | ±0.5 dB
[Note 2] | 300 ns | +| OLT receive power
[Note 3] | –34 to –8 dBm | 0.1 dB | ±2 dB | ±0.5 dB
[Note 2] | 300 ns | + +NOTE 1 – The typical range attempts to capture the most common range of parameters of an operational optical module. If a module has a different operational range, then the measurement range should follow that range, augmented by the measurement inaccuracy on either end. + +NOTE 2 – ONT and OLT optical repeatability refers to multiple measurements taken when the true values of the ONT or OLT temperature and voltage are the same at the time of measurement. However, the normal range of those parameters should be exercised in between tests as a means to gauge their aging effects. + +NOTE 3 – The measurement of the OLT should reflect the average power received during a burst. This requires the OLT to perform the measurement at the proper time with respect to the incoming burst, and that said burst is long enough to support the response time of the detector. The deviation due to non-50% duty cycle in the upstream data pattern is not to be charged against the measurement accuracy or repeatability specifications. + +NOTE 4 – Nominal refers to the design value of the quantity being measured (i.e., voltage or bias current) for the particular device implementation. + +## **B.4 OLS physical layer performance measurements requirements** + +All parameters in clauses B.2 and B.3 should be monitored continuously in real time in order to reflect the actual quality of physical links and operational status of optical modules. Moreover, the monitoring process should not significantly degrade the normal service transmissions. + +## Appendix I + +## Allocation of the physical layer overhead time + +(This appendix forms an integral part of this Recommendation.) + +The physical layer overhead ( $T_{plo}$ ) time is used to accommodate five physical processes in the PON. These are: laser on/off time; timing drift tolerance; level recovery; clock recovery; and start of burst delimitation. The exact division of the physical layer time to all these functions is determined partly by constraint equations, and partly by implementation choices. This appendix reviews the constraints with which the OLT must comply, and suggests values for the discretionary values. + +As shown in Table I.2, specific values for $T_{on}$ , $T_{off}$ , and $T_{plo}$ are given for the different data rates. $T_{plo}$ can be divided into three sections with respect to what ONT data pattern is desired. For simplicity, these times can be referred to as the guard time ( $T_g$ ), the preamble time ( $T_p$ ) and the delimiter time ( $T_d$ ). During $T_g$ , the ONT will transmit no more power than the nominal zero level. During $T_p$ , the ONT will transmit a preamble pattern that provides maximal transition density for fast level and clock recovery functions. Lastly, during $T_d$ , the ONT will transmit a special data pattern with optimal autocorrelation properties that enable the OLT to find the beginning of the burst. + +An additional parameter of the control logic on the PON is the total peak-to-peak timing uncertainty ( $T_u$ ). This uncertainty arises from variations of the time of flight caused by fibre and component variations with temperature and other environmental factors. + +The constraint conditions with which the OLT must comply are then: + +$$T_g > T_{on} + T_u, \text{ and}$$ + +$$T_g > T_{off} + T_u$$ + +$T_d$ must provide sufficient data bits to provide a robust delimiter function in the face of bit errors. The error resistance of the delimiter depends on the exact implementation of the pattern correlator, but a simple approximate relationship between the number of bits in the delimiter ( $N$ ) and the number of bit errors tolerated ( $E$ ) is: + +$$E = \text{int}(N/4) - 1 \quad (\text{I-1})$$ + +Equation I-1 has been empirically verified by a numerical search of all the delimiters of sizes ranging from 8 to 20 bits. This search was performed under the assumption that the preamble pattern was a "1010" repeating pattern, and that the delimiter has an equal number of 0s and 1s. The Hamming distance, $D$ , of the best delimiter from all shifted patterns of itself and the preamble was found to be $D = \text{int}(N/2) - 1$ ; yielding the error tolerance shown. + +Given a certain bit error rate (BER), the probability of a severely errored burst ( $P_{seb}$ ) is given by: + +$$P_{seb} = \left( \frac{N}{E+1} \right) \text{BER}^{E+1} \quad (\text{I-2})$$ + +Substituting Equation I-1 into Equation I-2, the resultant $P_{seb}$ is given by: + +$$P_{seb} = \left[ \frac{N}{\text{int}(N/4)} \right] \text{BER}^{\text{int}(N/4)} \quad (\text{I-3})$$ + +If the BER equals $1E - 4$ , the resultant $P_{seb}$ for various delimiter lengths, $N$ , are given in Table I.1. Inspection of Table I.1 shows that, in order to suppress this kind of error, the delimiter length must be at least 16 bits, if not more. + +**Table I.1 – Probability of a severely errored burst as a function of delimiter length** + +| $N$ | $P_{\text{seb}}$ | +|-----|------------------| +| 8 | $2.8E - 07$ | +| 12 | $2.2E - 10$ | +| 16 | $1.8E - 13$ | +| 20 | $1.5E - 16$ | +| 24 | $1.3E - 19$ | + +With these considerations taken into account, the recommended allocations of the physical layer overhead are given in Table I.2, which also lists the normative values for the ONT Tx enable time and Tx disable time, as well as the total physical layer overhead time for reference. + +**Table I.2 – Recommended allocation of burst mode overhead time for OLT functions** + +| Upstream data rate (Mbit/s) | Tx enable (bits) | Tx disable (bits) | Total time (bits) | Guard time (bits) | Preamble time (bits) | Delimiter time (bits) | +|-----------------------------|------------------|-------------------|-------------------|-------------------|----------------------|-----------------------| +| 155.52 | 2 | 2 | 32 | 6 | 10 | 16 | +| 622.08 | 8 | 8 | 64 | 16 | 28 | 20 | +| 1 244.16 | 16 | 16 | 96 | 32 | 44 | 20 | +| 2 488.32 | 32 | 32 | 192 | 64 | 108 | 20 | +| Notes | Maximum | Maximum | Mandatory | Minimum | Suggested | Suggested | + +# Appendix II + +## Description and examples of power levelling mechanism + +(This appendix forms an integral part of this Recommendation.) + +## II.1 Introduction + +This appendix illustrates the different considerations that have to be taken into account in order to perform a stable and efficient power levelling mechanism. They lead to the requirements of clause 8.3.2. + +### II.2 ONU levels + +The ONU transmitter power (mean launched MIN and MAX) is described in Table 2f-2 and g-2. These values correspond to mode 0. The values corresponding to mode 1 and mode 2 are 3 dB and 6 dB lower, respectively. As an example, a class B ONU for 1 244 Mbit/s with power levelling capability will comply to the following output power ranges: + +Mode 0: $\text{MIN} = -2 \text{ dBm} \leq \text{mean launched power} \leq \text{MAX} = +3 \text{ dBm}$ + +Mode 1: $\text{MIN} = -5 \text{ dBm} \leq \text{mean launched power} \leq \text{MAX} = 0 \text{ dBm}$ + +Mode 2: $\text{MIN} = -8 \text{ dBm} \leq \text{mean launched power} \leq \text{MAX} = -3 \text{ dBm}$ + +The power levelling mechanism is under control of the OLT and determines the necessary level changes. When an ONU receives an order to change from one mode to another, it will be able to set its emitted power to the corresponding range of the new mode and will then resume sending upstream data. Note that as long as the ranges are respected, the effective change of ONU power from one mode to another does not necessarily have to be equal to the 3 dB or 6 dB step. + +#### *Example 1* + +- An ONU in mode 1 is emitting at $-1 \text{ dBm}$ . +- This ONU receives a message to go to mode 0 (increase setting by $+3 \text{ dB}$ ). +- The effective emitted power is now $+1 \text{ dBm}$ , not exactly 3 dB higher, but within the range of mode 0. + +#### *Example 2* + +- An ONU in mode 2 is emitting at $-4 \text{ dBm}$ . +- The ONU receives a message to go to mode 1 (increase setting by $+3 \text{ dB}$ ). +- The effective emitted power is now $-5 \text{ dBm}$ , lower than the previous power, but within the range of mode 1. +- The OLT will measure a lower power while it expected a higher power. The algorithm in the OLT will therefore send another command to increase by 3 dB (go to mode 0). +- The ONU will now emit within the range of mode 0, which is min. $-2 \text{ dBm}$ . + +### II.3 Thresholds at OLT + +The OLT receiver measures the incoming power level for a particular ONU and compares it to thresholds. There will be an uncertainty on this measurement, due to implementation-specific inaccuracies (current sources, linearity of receiver at high power, supply voltage variations, temperature effects on the electrical amplifier stages, etc.). This translates into uncertainties on the effective threshold value when compared to its setting. These uncertainties have to be taken into account to guarantee a comprehensive and stable power levelling mechanism. The uncertainty range + +over which the threshold can vary over the full operational range of the OLT is required to be max. 4 dB. + +Taking into account the values of the optical power corresponding to the OLT Rx minimum sensitivity $P_{ms}$ and minimum overload $P_{mo}$ stated in Table 2f-2 and g-2, the allowed power range at the OLT receiver for correct operation is then ( $P_{ms} + 1$ dB) through $P_{mo}$ . Note that $P_{ms}$ includes a 1 dB penalty (see clause 8.2.8.3), which does not have to be considered for the minimal optical power. A correct power at the OLT receiver must be guaranteed by the power levelling mechanism. There are two cases for the mechanism: single threshold and double threshold. + +#### II.3.1 Case 1: Comparison to two thresholds (TL, TH) + +In this case, the power levelling mechanism is implemented by comparing the received average power at the OLT ( $P$ ) to two different thresholds (TL and TH). When $P < TL$ , the power at the OLT is considered too low and the ONU must go to a higher mode. When $P > TH$ , the power at the OLT is considered too high and the ONU must go to a lower mode. When $TH > P > TL$ , the power at the OLT is considered fine and the ONU can be kept at its current mode. + +1) The effective value of TH must guarantee the following. + +- Any power level above the OLT receiver overload is detected: $P_{mo} > TH$ . +- If an ONU goes into a lower mode because $P > TH$ , the OLT receiver may not go below sensitivity: + +$$TH > P_{mo} - [(P_{mo} - P_{ms} - 1 \text{ dB}) - 3 \text{ dB} - (P_{ONU \text{ Tx MAX}} - P_{ONU \text{ Tx MIN}})].$$ + +This is equal to: $TH > P_{mo} - 6 \text{ dB}$ . + +2) The effective value of TL must guarantee the following. + +- Any power level below OLT receiver sensitivity is detected: $TL > P_{ms} + 1 \text{ dB}$ . +- If an ONU goes into a higher mode because $P < TL$ , the OLT receiver may not go into overload: + +$$(P_{ms} + 1 \text{ dB}) + [(P_{mo} - P_{ms} - 1 \text{ dB}) - 3 \text{ dB} - (P_{ONU \text{ Tx MAX}} - P_{ONU \text{ Tx MIN}})] > TL.$$ + +This is equivalent to: $P_{ms} + 7 \text{ dB} > TL$ . + +3) The combined effective values of TL and TH must guarantee that: + +- the mechanism is stable (no repetitive toggling between modes). If an ONU changes to another mode because $P < TL$ or $P > TH$ , the new power level at the OLT receiver may not cross the opposite threshold. This is equivalent to defining a minimum spacing between TH and TL. + +$$TH - TL > 3 \text{ dB} + (P_{ONU \text{ Tx MAX}} - P_{ONU \text{ Tx MIN}}).$$ + +This is equivalent to: $TH - TL > 8 \text{ dB}$ . + +This last combined requirement tightens the individual requirements for TH and TL, as they should be spaced by at least 8 dB. Taking into account the requirement of the uncertainty margin of max. 4 dB, the best fit for the first and second requirements (largest spacing between TH and TL) then becomes: + +$$R1: P_{mo} > TH > P_{mo} - 4 \text{ dB}.$$ + +$$R2: P_{ms} + 5 \text{ dB} > TL > P_{ms} + 1 \text{ dB}.$$ + +As R1 and R2 only guarantee a spacing of 6 dB, the third requirement must also be kept: + +$$R3: TH - TL > 8 \text{ dB}.$$ + +R1, R2 and R3 together allow for a variation of TH and TL over 4 dB over the full operational range of the OLT (temperature, ...) but require at any moment that TH and TL be spaced by at least 8 dB. + +If an OLT has a more precise power measurement than 4 dB, any combination of TH and TL can be chosen as long as R1, R2 and R3 are respected. + +#### II.3.2 Case 2: Comparison to one threshold (TL) + +The power levelling mechanism is implemented by starting all ONUs at mode 2 (during their initialization) and comparing the received average power at the OLT ( $P$ ) to one threshold (TL). When $P < TL$ , the power at the OLT is considered too low and the ONU must go to a higher mode. When $P > TL$ , the power at the OLT is considered fine and the ONU can be kept in its current mode. + +The effective value of TL must guarantee the following. + +- Any power level under OLT receiver sensitivity is detected: $TL > P_{ms} + 1$ dB. +- If an ONU goes into a higher mode because $P < TL$ , the OLT receiver may not go into overload: + +$$(P_{ms} + 1 \text{ dB}) + [(P_{mo} - P_{ms} - 1 \text{ dB}) - 3 \text{ dB} - (P_{ONU \text{ Tx MAX}} - P_{ONU \text{ Tx MIN}})] > TL.$$ + +This is equal to: $P_{ms} + 7 \text{ dB} > TL$ . + +Therefore the requirement for the effective level TL is: + +$$R2: P_{ms} + 7 \text{ dB} > TL > P_{ms} + 1 \text{ dB}.$$ + +With an uncertainty range of 4 dB, this leaves a choice for the TL setting: + +Example 1 for class B at 1 244 Mbit/s: $-23 \text{ dBm} > TL > -27 \text{ dBm}$ ; + +Example 2 for class B at 1 244 Mbit/s: $-21 \text{ dBm} > TL > -25 \text{ dBm}$ . + +## II.4 Power detection + +In order to initialize new ONUs, the OLT periodically opens ranging windows during which new ONUs can send upstream bursts. The OLT must be able to detect the presence of any new ONU. This implies that when new ONUs start at mode 2, the OLT must be capable to detect (but not necessarily read data at) an optical power as weak as $(P_{ms} + 1 \text{ dB}) - 6 \text{ dB} = P_{ms} - 5 \text{ dB}$ . + +## **Appendix III** + +(This appendix does not form an integral part of this Recommendation.) + +The material formerly in Appendix III is now contained in Annex A. + +## **Appendix IV** + +(This appendix does not form an integral part of this Recommendation.) + +The material formerly in Appendix IV is now contained in Annex B. + +# Appendix V + +## Industry best practice for single-sided extended 2.488 Gbit/s downstream, 1.244 Gbit/s upstream GPON (class C+ and class D) + +(This appendix does not form an integral part of this Recommendation.) + +## V.1 Introduction + +The single-sided extended 2.488/1.244 Gbit/s GPON is achieved by using a more capable OLT interface. This interface would have all the characteristics of the existing S/R interface, with the exception of certain OLT optical parameters, as listed in Table V.1 (for class C+) or Table V.2 (for class D). Note that the ONU specifications should be achievable with ONU optics that are substantially similar to those described in Annex A, except for the difference in upstream wavelength (described in [ITU-T G.984.5]) and operation with FEC (described in [ITU-T G.984.3]). + +**Table V.1 – Optical power levels for the 2.488 Gbit/s downstream, 1.244 Gbit/s upstream single-sided reach extended system (Class C+)** + +| Item | Unit | Single fibre | +|-------------------------------------------|----------|--------------| +| Reach-extended OLT: | | OLT | +| Mean launched power MIN | dBm | +3 | +| Mean launched power MAX | dBm | +7 | +| Downstream optical penalty | dB | 1 | +| Bit error ratio (pre-FEC) [Note 1] | | $10^{-4}$ | +| Minimum sensitivity [Note 1] | dBm | -32 | +| Minimum overload | dBm | -12 | +| Upstream wavelength range [ITU-T G.984.5] | nm | 1 290-1 330 | +| ONU: | – | ONU | +| Mean launched power MIN | dBm | +0.5 | +| Mean launched power MAX | dBm | +5 | +| Upstream optical penalty | dB | 0.5 | +| Upstream wavelength range [ITU-T G.984.5] | nm | 1 290-1 330 | +| Bit error ratio (pre-FEC) [Note 2] | – | $10^{-4}$ | +| Minimum sensitivity [Note 2] | dBm | -30 | +| Minimum overload [Note 3] | dBm | -8 | + +NOTE 1 – The OLT sensitivity assumes the use of the optional RS (255,239) FEC capability of the GPON TC layer, as well as intrinsic detector technology improvements, e.g., SOA preamplification. + +NOTE 2 – The ONU sensitivity assumes the use of the optional RS (255,239) FEC capability of the GPON TC layer with the current class B+ ONU detector technology. + +NOTE 3 – The ONU overload is set at -8 dBm to be common with the class B+ value, even though in this application -10 dBm is sufficient. + +**Table V.2 – Optical power levels for the 2.488 Gbit/s downstream, 1.244 Gbit/s upstream single-sided reach extended system (Class D)** + +| Item | Unit | Single fibre | +|-------------------------------------------|------|--------------| +| Reach-extended OLT: | | OLT | +| Mean launched power MIN | dBm | +6 | +| Mean launched power MAX | dBm | +10 | +| Downstream optical penalty | dB | 1 | +| Bit error ratio (pre-FEC) [Note 1] | | $10^{-4}$ | +| Minimum sensitivity [Note 1] | dBm | -35 | +| Minimum overload | dBm | -15 | +| Upstream wavelength range [ITU-T G.984.5] | nm | 1 290-1 330 | +| ONU: | – | ONU | +| Mean launched power MIN | dBm | +0.5 | +| Mean launched power MAX | dBm | +5 | +| Upstream optical penalty | dB | 0.5 | +| Upstream wavelength range [ITU-T G.984.5] | nm | 1 290-1 330 | +| Bit error ratio (pre-FEC) [Note 2] | – | $10^{-4}$ | +| Minimum sensitivity [Note 2] | dBm | -30 | +| Minimum overload [Note 3] | dBm | -8 | + +NOTE 1 – The OLT sensitivity assumes the use of the optional RS (255,239) FEC capability of the GPON TC layer, as well as intrinsic detector technology improvements, e.g., SOA preamplification. + +NOTE 2 – The ONU sensitivity assumes the use of the optional RS (255,239) FEC capability of the GPON TC layer with the current class B+ ONU detector technology. + +NOTE 3 – The ONU overload is set at -8 dBm to be common with the class B+ value, even though in this application -10 dBm is sufficient. + +The single-sided extended ODN link budget for class C+ is given in Table V.3, and for class D is given in Table V.4. These budgets covers all optical components between the extended OLT and ONU, including non-integrated WDM filters for the multiplex of video overlays and other enhancement band services, and must include any Raman impairment from the overlay signal. + +**Table V.3 – Loss budgets for the single-sided extended GPON system (class C+)** + +| Items | Unit | Single fibre | +|----------------------------------|------|--------------| +| Minimum optical loss at 1 490 nm | dB | 17 | +| Minimum optical loss at 1 310 nm | dB | 17 | +| Maximum optical loss at 1 490 nm | dB | 32 | +| Maximum optical loss at 1 310 nm | dB | 32 | +| Maximum fibre length | km | 60 | + +**Table V.4 – Loss budgets for the single-sided extended GPON system (class D)** + +| Items | Unit | Single fibre | +|----------------------------------|-------------|---------------------| +| Minimum optical loss at 1 490 nm | dB | 20 | +| Minimum optical loss at 1 310 nm | dB | 20 | +| Maximum optical loss at 1 490 nm | dB | 35 | +| Maximum optical loss at 1 310 nm | dB | 35 | +| Maximum fibre length | km | 60 | + +# Bibliography + +- [b-ITU-T G.957] Recommendation ITU-T G.957 (2006), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy*. + + + + + +## 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.987.2-202302-I_PDF-E/02ab1c6abcb5a2d487a30d019a5454b6_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/02ab1c6abcb5a2d487a30d019a5454b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ca6fee73bdc61126b76d7c7a925172fbcae8286 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/02ab1c6abcb5a2d487a30d019a5454b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c9b8fb2348782367fdff5cf188a51bc498e2245123bc9f345ad7ed21ad67b75 +size 46929 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/124c6108c63173818afb8ed49521e22d_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/124c6108c63173818afb8ed49521e22d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da51cbcaa0aa73916928e1747cfa8140d45584f5 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/124c6108c63173818afb8ed49521e22d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1a6037cea558369e4ffcd3c3db59a385749be2dda996b8c084553c3ee9c7305 +size 18721 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/250cf77a1cd51989da09fca796b3e4ea_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/250cf77a1cd51989da09fca796b3e4ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..413297190b87463b50815265d630e4b4ea8e0ac5 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/250cf77a1cd51989da09fca796b3e4ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e09b6c074f366d044b6ff855375bc968ac3bff19f7972195aa7b5c4411de360 +size 32921 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/2a77eb32ef4c4d8a5c1758a53a908336_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/2a77eb32ef4c4d8a5c1758a53a908336_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa0fc712cf268ff161c14970dec4aee7019332ae --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/2a77eb32ef4c4d8a5c1758a53a908336_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51b7e391701c03bdbd063580126b51523eb0e04f51cbe6313e9988dd21f9dbd5 +size 43899 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f71064c63e95ac4227107bf93363aa47c248fcd4 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b433cbfb6a6a9b435bff50a5d597c19803dfbea86fd675894394769c72e6c2d +size 79585 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14ec0872f8d8e26f3b698c44836d0effa4500624 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b70f34b06404170edb07a3ff8fdc7b58772260dd6e3f3efd2cefa57c30f354c +size 85405 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/595e9fd7e96f6b95bbaa6e6a45c32682_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/595e9fd7e96f6b95bbaa6e6a45c32682_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf1818134cf577167c1c7f5548b9be4ddc61f09b --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/595e9fd7e96f6b95bbaa6e6a45c32682_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c30a2f36cbd1a518a066aa2d392647b0e610425f6191011b3f02b17ebf6c65a8 +size 34958 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/5ed9189841659dfb01f809b8e3b21f74_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/5ed9189841659dfb01f809b8e3b21f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..deacd5fe4f8e2bad21b18eed98b12a1aab12f4c5 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/5ed9189841659dfb01f809b8e3b21f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5564cb094b132bfdf96b1c697d8dd2eda0abacbd7f0a15a9f5e992a26cfa6455 +size 41786 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/60e9207be66a64332619bb4b667fe67b_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/60e9207be66a64332619bb4b667fe67b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cd0ddd42457333f0d6d793275787d429f134c6a --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/60e9207be66a64332619bb4b667fe67b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf57316499911b35383857b56f74e5582d1ec936be9f28925f516b23746e92fa +size 49685 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/6ee57fd30c7e609827c2a11d0983eeba_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/6ee57fd30c7e609827c2a11d0983eeba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1e10748bc6d8abd42952adb1edfbbfcb8957928 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/6ee57fd30c7e609827c2a11d0983eeba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d59caf9acfc180b5928c0769c93e935d024b0938406520b7f41bef7d487a7fb +size 57729 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1520e06257f3b3ab855cbe603bd59c1248c33d8 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a8c2c77911dab41dd32a9704c05d0a18163b2953784442155cd095736949266 +size 20636 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02c2e2cbc3571e5e491d59ee192a150e471c1c0f --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a5d33929a0ee43dfa7b588952959f6f39b9628fa59402f86691885947d69cad +size 23690 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db1ed32a4fdc10165188f8647b41292e0cae0335 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db488b752a33847ade80a994e823239c13d282343ca2c5afaedf3a98798725ba +size 58615 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/a1890b9a9b85f13e67ed59bbad623659_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51dacbe0e881cd57fd158f06ecdf234bcf3d6e25 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/a1890b9a9b85f13e67ed59bbad623659_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ebdaf99ac87fac162c8aca7094d203925b573a1f9bebb4bab0ed59efc881aee +size 62818 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2729de583b8f86fee81ded841885214b176ec78 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d6be80ce7045a4e52b98f5f16b83a3c043307f52773f6b4758864af36db0ad1 +size 91391 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3f7bf7d84e2550da6c97a8319d9b4037aa9362f --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3112d52ca65737a88e23ec40bdd03a070eb3f6466176cd9a8eed9dd716cb5cda +size 37088 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70cdbe5f3943076e5e53372e91bcc895aa64b7fb --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67ce9e192d89691a892dbebed92d11f0dc50d90b6e86c9827ef5bd8d5395f0d1 +size 45813 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/f880daa1cde4b71fcbaff2df81803a65_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/f880daa1cde4b71fcbaff2df81803a65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f533cf2694825c20a3e03d43b34602b94e825f2 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/f880daa1cde4b71fcbaff2df81803a65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8809da2a39fef3bc8bb13e6a432a8f37562d4ea5ef3f75598a32855a3198bf42 +size 21430 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/G/T-REC-G.987.2-202302-I_PDF-E/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e60f5d3411dc0348fffce61248e51d283508e056 --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1114e6ce7ffcab33e453676fbd6c4b4baac047efa985747f3fbaa71d14eb63c1 +size 56037 diff --git a/marked/G/T-REC-G.987.2-202302-I_PDF-E/raw.md b/marked/G/T-REC-G.987.2-202302-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e194d314dcd9249bc4cce319ce3d9717ace660ad --- /dev/null +++ b/marked/G/T-REC-G.987.2-202302-I_PDF-E/raw.md @@ -0,0 +1,1269 @@ + + +# Recommendation**ITU-T G.987.2 (02/2023)** + +SERIES G: Transmission systems and media, digital systems and networks + +Digital sections and digital line system – Optical line systems for local and access networks + +--- + +### **10-Gigabit-capable passive optical networks (XG-PON): Physical media dependent (PMD) layer specification** + + + +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 superimposed 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 | +| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | +| General | G.900–G.909 | +| Parameters for optical fibre cable systems | G.910–G.919 | +| Digital sections at hierarchical bit rates based on a bit rate of 2048 kbit/s | G.920–G.929 | +| Digital line transmission systems on cable at non-hierarchical bit rates | G.930–G.939 | +| Digital line systems provided by FDM transmission bearers | G.940–G.949 | +| Digital line systems | G.950–G.959 | +| Digital section and digital transmission systems for customer access to ISDN | G.960–G.969 | +| Optical fibre submarine cable systems | G.970–G.979 | +| Optical line systems for local and access networks | G.980–G.989 | +| Metallic access networks | G.990–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.987.2 + +# 10-Gigabit-capable passive optical networks (XG-PON): Physical media dependent (PMD) layer specification + +## Summary + +Recommendation ITU-T G.987.2 describes the physical layer requirements and specifications for the XG-PON physical media dependent (PMD) layer. Wavelength enhancement bands are described in Recommendation ITU-T G.987.1. The transmission convergence (TC) layer is described in Recommendation ITU-T G.987.3. The optical network unit (ONU) management and control interface (OMCI) specifications are described in Recommendation ITU-T G.988. + +Recommendation ITU-T G.987.2 describes a flexible optical fibre access network capable of supporting the bandwidth requirements of business and residential services. The G.987 series of standards allows for multiple upstream and downstream line rates. This Recommendation currently defines one type of 10-Gigabit-capable passive optical network (XG-PON) system with an asymmetric nominal line rate of 9.95328 Gbit/s in the downstream direction and 2.48832 Gbit/s in the upstream direction. + +This Recommendation describes a system that represents an evolutionary development from the systems described in the ITU-T G.984 series. To the greatest extent possible, this Recommendation maintains the requirements of Recommendation ITU-T G.984.1 to ensure maximal continuity with existing systems and optical fibre infrastructure. + +Amendment 2 continues the maintenance and evolution of physical media dependent (PMD) layer specifications for XG-PON as defined in this Recommendation. It includes technical updates and corrections for changing references to XG-PON1 to XG-PON, replacing the mask of the eye diagram for the ONU transmitter, updating the DD40 downstream specification, correcting the X/S tolerance mask for ONU and updating the X/S tolerance mask for the optical trunk line (OLT). + +This revision adds a new annex specifying out-of-band noise limits on XG-PON ONUs to reduce the impact on other systems coexisting on the same PON. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|-----------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.987.2 | 2010-01-13 | 15 | 11.1002/1000/10411 | +| 2.0 | ITU-T G.987.2 | 2010-10-07 | 15 | 11.1002/1000/10889 | +| 2.1 | ITU-T G.987.2 (2010) Amd. 1 | 2012-02-13 | 15 | 11.1002/1000/11499 | +| 3.0 | ITU-T G.987.2 | 2016-02-26 | 15 | 11.1002/1000/12832 | +| 3.1 | ITU-T G.987.2 (2016) Amd. 1 | 2017-08-13 | 15 | 11.1002/1000/13290 | +| 3.2 | ITU-T G.987.2 (2016) Amd. 2 | 2020-10-29 | 15 | 11.1002/1000/14491 | +| 4.0 | ITU-T G.987.2 | 2023-02-22 | 15 | 11.1002/1000/15124 | + +## Keywords + +10-Gigabit-capable passive optical network, FTTx network, OLT, ONU, optic, optical network terminal (ONT), passive optical network (PON), physical layer interfaces, physical layer requirements, physical layer specification, PMD, XG-PON. + +--- + +\* To access the Recommendation, type the URL
(N1 class) | Nominal2 class
(N2 class) | Extended1 class
(E1 class) | Extended2 class
(E2 class) | +|--------------|--------------------------------------|--------------------------------------|---------------------------------------|---------------------------------------| +| Minimum loss | 14 dB | 16 dB | 18 dB | 20 dB | +| Maximum loss | 29 dB | 31 dB | 33 dB | 35 dB | + +For single-star architectures, the absence of optical branching devices may result in optical path losses of less than 5 dB. In such a case, the ODN must contain additional optical attenuators guaranteeing minimum channel insertion loss for the given class to prevent potential damage to receivers. + +## 6.2 Categories for fibre differential distance + +Categories for fibre differential distance + +Recommended categories for fibre differential distance (DD) are shown in Table 6-2. + +**Table 6-2 – Categories for fibre differential distance defined in G.987.2** + +| | DD20 | DD40 | +|-------------------------------|-------------|-------------| +| Maximum differential distance | 20 km | 40 km | + +For DD40 ODNs, due to the intrinsic wavelength dependence of the optical fibre loss [ITU-T G.652], the fibre attenuation coefficient at the downstream wavelength (1577 nm) is lower than that at the upstream wavelength (1270 nm) resulting in a downstream loss margin. This margin is expected to be at least 1 dB for a fibre length greater than 20 km. The additional maximum optical path penalty allowed for DD40 is therefore fully compensated by the lower fibre loss at the downstream wavelength. Thus, the other PMD values (except optical path penalty (OPP)) for DD40 do not change from those PMD values specified for DD20. + +In DD40 deployments, the actual fibre cable loss characteristics should be assessed, to make sure there is the required extra margin of 1dB with respect to the maximum OPL class loss at the downstream wavelength for ODN branches with a maximum OLT-ONU fibre length greater than 20 km. + +# 7 Services + +See clause 7 of [ITU-T G.987.1]. + +# 8 User-network interface and service node interface + +See Appendix I of [ITU-T G.987.1]. + +# 9 Optical network requirements + +## 9.1 Layered structure of XG-PON optical network + +See clause 5.2.5 of [ITU-T G.987.1]. + +## 9.2 Physical media dependent layer requirements for the XG-PON + +All parameters are specified as follows, and are in accordance with Tables 9-2 to 9-4. + +There are two ONU types, based on different ONU receiver sensitivity. + +All parameter values specified are worst-case values, to be met over the range of standard operating conditions (i.e., temperature and humidity), 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 the values specified in Table 9-3 and Table 9-4, for the extreme case of optical path attenuation and dispersion conditions. + +In particular, the values given in Table 9-3 and Table 9-4 are valid for the cases of an enhancement band, as described in clause 10. + +### 9.2.1 Line rate + +The transmission line rate is a multiple of 8 kHz. The target standardized 10-gigabit-capable passive optical network (XG-PON) system supports the following variant: XG-PON with a downstream line rate of 9.95328 Gbit/s and an upstream line rate of 2.48832 Gbit/s. + +Parameters to be defined are categorized by downstream and upstream, and the nominal line rate as shown in Table 9-1. + +**Table 9-1 – Relation between parameter categories and tables** + +| Variant | Transmission direction | Nominal line rate [Gbit/s] | Reference table | +|---------|------------------------|----------------------------|-----------------| +| XG-PON | Downstream | 9.95328 | Table 9-3 | +| | Upstream | 2.48832 | Table 9-4 | + +##### 9.2.1.1 Downstream accuracy + +When the optical trunk line (OLT) and the end office are in their normal operating state, the OLT is typically traceable to a Stratum-1 reference (accuracy of $1 \times 10^{-11}$ ). When the OLT is in its free-running mode, the accuracy of the downstream signal is at least that of a Stratum-4 clock ( $3.2 \times 10^{-5}$ ). OLTs intended for timing-critical applications such as mobile backhaul may require stratum-3 quality in free-running mode. + +NOTE – The OLT may derive its timing from either a dedicated timing signal source or from a synchronous data interface (line timing). A packet-based timing source may also be used. + +##### 9.2.1.2 Upstream accuracy + +When in one of its operating states and granted an allocation, the ONU shall transmit its signal with frequency accuracy equal to that of the received downstream signal. + +#### 9.2.2 Forward error correction code selection for XG-PON + +See clause 10.3 of [ITU-T G.987.3]. + +#### 9.2.3 Physical media and transmission method + +##### 9.2.3.1 Transmission medium + +This Recommendation is based on the fibre described in [ITU-T G.652]. Other fibre types may be compatible with this Recommendation, e.g., [ITU-T G.657], used, for example, for in-building cabling, drop section. + +##### 9.2.3.2 Transmission direction + +The signal is transmitted both upstream and downstream through the transmission medium. + +##### 9.2.3.3 Transmission methodology + +Bidirectional transmission is accomplished by use of wavelength division multiplexing (WDM) technique on a single fibre. + +#### 9.2.4 Line code + +The scrambling method is defined in [ITU-T G.987.3]. + +The convention used for optical logic levels is: + +- high level of light emission for a binary ONE; +- low level of light emission for a binary ZERO. + +##### 9.2.4.1 Downstream + +Downstream line coding for XG-PON: NRZ. + +##### 9.2.4.2 Upstream + +Upstream line coding for XG-PON: NRZ. + +#### 9.2.5 Operating wavelength + +##### 9.2.5.1 Downstream wavelength allocation + +The operating wavelength range for XG-PON for the downstream direction is defined in Table 9-3. + +##### 9.2.5.2 Upstream wavelength allocation + +The operating wavelength range for XG-PON for the upstream direction is defined in Table 9-4. + +#### 9.2.6 XG-PON PMD parameters + +##### 9.2.6.1 XG-PON compatible ODN + +XG-PON shall operate over an ODN whose parameters are described by Table 9-2. + +**Table 9-2 – Physical parameters of a simple ODN (ODS)** + +| Item | Unit | Specification | +|---------------------------------------------------|------|----------------------------------------------------------------------------------| +| Fibre type (Note) | – | [ITU-T G.652], or compatible | +| Attenuation range (as defined in clause 6.1) | dB | N1 class: 14 – 29
N2 class: 16 – 31
E1 class: 18 – 33
E2 class: 20 – 35 | +| Maximum fibre distance between S/R and R/S points | km | DD20: 20
DD40: 40 | +| Minimum fibre distance between S/R and R/S points | km | 0 | +| Bidirectional transmission | – | 1-fibre WDM | +| Maintenance wavelength | nm | See [ITU-T L.313] | +| NOTE – See clause 9.2.3.1 | | | + +##### 9.2.6.2 Optical interface parameters of 9.95328 Gbit/s downstream direction + +**Table 9-3 – Optical interface parameters of 9.95328 Gbit/s downstream direction** + +| Item | Unit | Value | +|-------------------------------------------------------------------------------------------------|--------|----------------------| +| OLT transmitter (optical interface Old) | | | +| Nominal line rate | Gbit/s | 9.95328 | +| Operating wavelength (Note 1) | nm | 1575 – 1580 | +| Line code | – | NRZ | +| Mask of the transmitter eye diagram | – | see clause 9.2.7.6.1 | +| Maximum reflectance at S/R, measured at transmitter wavelength | dB | NA | +| Minimum optical return loss (ORL) of ODN at O lu and O ld (Notes 2 and 3) | dB | more than 32 | + +**Table 9-3 – Optical interface parameters of 9.95328 Gbit/s downstream direction** + +| Item | Unit | Value | | | | | | +|-------------------------------------------------------------|-------|------------------------------|-------|-------|-------|-------|-------| +| ODN Class | | N1 | N2 | | E1 | E2 | | +| | | | N2a | N2b | | E2a | E2b | +| Mean launched power MIN | dBm | +2.0 | +4.0 | +10.5 | +6 | +8 | +14.5 | +| Mean launched power MAX | dBm | +6.0 | +8.0 | +12.5 | +10 | +12 | +16.5 | +| Launched optical power without input to the transmitter | dBm | NA | | | | | | +| Minimum extinction ratio | dB | 8.2 | | | | | | +| Transmitter tolerance to reflected optical power (Note 7) | dB | more than -15 | | | | | | +| Dispersion Range | ps/nm | 0-400 (DD20)
0-800 (DD40) | | | | | | +| Minimum side-mode-suppression ratio | dB | 30 | | | | | | +| Maximum differential optical path loss | dB | 15 | | | | | | +| Jitter generation | – | see clause 9.2.9.7.3 | | | | | | +| ONU receiver (optical interface O id ) | | | | | | | | +| Maximum OPP (Note 6, Note 9) | dB | 1.0 (DD20)
2.0 (DD40) | | | | | | +| Maximum reflectance at R/S, measured at receiver wavelength | dB | less than -20 | | | | | | +| BER reference level | – | 10 -3 (Note 4) | | | | | | +| ODN Class | | N1 | N2 | | E1 | E2 | | +| | | | N2a | N2b | | E2a | E2b | +| Minimum sensitivity at BER reference level (Note 5) | dBm | -28.0 | -28.0 | -21.5 | -28.0 | -28.0 | -21.5 | +| Minimum overload at BER reference level | dBm | -8.0 | -8.0 | -3.5 | -8.0 | -8.0 | -3.5 | +| Consecutive identical digit immunity | bit | more than 72 | | | | | | +| Jitter tolerance | – | see clause 9.2.9.7.2 | | | | | | +| Receiver tolerance to reflected optical power (Note 8) | dB | less than 10 | | | | | | + +NOTE 1 – In the case of outdoor OLT deployment, it is allowed for the operating wavelength to span between 1 575 and 1 581 nm. + +NOTE 2 – There are optional cases where the "minimum optical return loss (ORL) of ODN at Olu and Oid" can be as low as 20 dB (see [b-ITU-T G.983.1] Appendix I). + +NOTE 3 – The value of ONU transceiver reflectance corresponding to the "minimum optical return loss (ORL) of ODN at Olu and Oid" is -20 dB (see [b-ITU-T G.983.1] Appendix II). + +NOTE 4 – See [b-ITU-T G Suppl.39], clause 9.4.1 for additional details. + +NOTE 5 – This sensitivity shall be met in the presence of G-PON and video overlay on the same ODN. If either G-PON, or video overlay, or both are absent, the sensitivity may be different (precise value is for further study). + +NOTE 6 – The specified penalty must be met by optics complying with the specified launched power range. If a transmitter exhibits a higher penalty, it can still comply if it equally increases the minimum + +**Table 9-3 – Optical interface parameters of 9.95328 Gbit/s downstream direction** + +| Item | Unit | Value | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------| +| launched power while remaining under the maximum launched power. In no case should the OPP exceed 2.5 dB. | | | +| NOTE 7 – Parameter known in [ITU-T G.984.2] as "Tolerance to the transmitter incident light power". | | | +| NOTE 8 – Parameter known in [ITU-T G.984.2] as "Tolerance to the reflected optical power". | | | +| NOTE 9 – For ODN branches with a maximum OLT-ONU fibre length greater than 20 km, the applicable maximum OPP is the DD40 value. However, the fibre loss at the downstream wavelength is lower than that at the upstream wavelength and this more than compensates for the extra OPP of DD40 vs. DD20 (i.e., the upstream wavelength loss limits the link distance and therefore loss margin exists for the downstream signal). For systems that connect ONUs at both short and long distances (up to 40 km) to the same OLT port, the optical link must comply with the DD20 maximum OPP value for ONUs at < =20 km and the DD40 maximum OPP value for ONUs at > 20 km. | | | + +##### 9.2.6.3 Optical interface parameters of 2.48832 Gbit/s upstream direction + +**Table 9-4 – Optical interface parameters of 2.48832 Gbit/s upstream direction** + +| Item | Unit | Value | | | | +|-------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------|------|------|------| +| ONU transmitter (optical interface Oru) | | | | | | +| Nominal line rate | Gbit/s | 2.48832 | | | | +| Operating wavelength | nm | 1260 – 1280 | | | | +| Line code | – | NRZ | | | | +| Mask of the transmitter eye diagram | – | see clause 9.2.7.6.2 | | | | +| Maximum reflectance at R/S, measured at transmitter wavelength | dB | less than –6 | | | | +| Minimum optical return loss (ORL) of ODN at O ru and O rd (Notes 1 and 2) | dB | more than 32 | | | | +| ODN Class | | N1 | N2 | E1 | E2 | +| Mean launched power MIN | dBm | +2.0 | +2.0 | +2.0 | +2.0 | +| Mean launched power MAX | dBm | +7.0 | +7.0 | +7.0 | +7.0 | +| Launched optical power without input to the transmitter (Note 3) | dBm | less than "Minimum sensitivity at BER reference level" – 10 | | | | +| Maximum Tx enable (Note 3) | bits | 32 | | | | +| Maximum Tx disable (Note 3) | bits | 32 | | | | +| Minimum extinction ratio | dB | 8.2 | | | | +| Transmitter tolerance to reflected optical power (Note 8) | dB | more than –15 | | | | +| Dispersion range (Note 4, Note 5) | ps/nm | 0 to –140 (DD20)
0 to –280 (DD40) | | | | +| Minimum side mode suppression ratio (Note 10) | dB | 30 | | | | +| Jitter transfer | – | see clause 9.2.9.7.1 | | | | +| Jitter generation | – | see clause 9.2.9.7.3 | | | | +| OLT receiver (optical interface Olu) | | | | | | +| Maximum OPP (Note 7) | dB | 0.5 | | | | + +**Table 9-4 – Optical interface parameters of 2.48832 Gbit/s upstream direction** + +| Item | Unit | Value | | | | +|--------------------------------------------------------|------|-------------------------------------------------------------|-------|---------------|-------| +| | | Maximum reflectance at S/R, measured at receiver wavelength | dB | less than –20 | | +| BER reference level | – | $10^{-4}$ (Note 6) | | | | +| ODN Class | | N1 | N2 | E1 | E2 | +| Minimum sensitivity at BER reference level | dBm | –27.5 | –29.5 | –31.5 | –33.5 | +| Minimum overload at BER reference level | dBm | –7.0 | –9.0 | –11 | –13 | +| Consecutive identical digit immunity | bit | more than 72 | | | | +| Jitter tolerance | – | see clause 9.2.9.7.2 | | | | +| Receiver tolerance to reflected optical power (Note 9) | dB | less than 10 | | | | + +NOTE 1 – There are optional cases where the "minimum optical return loss (ORL) of ODN at Oru and Ord" can be as low as 20 dB (see [b-ITU-T G.983.1] Appendix I). + +NOTE 2 – The value of ONU transceiver reflectance corresponding to the "minimum optical return loss (ORL) of ODN at Oru and Ord" is –20 dB (see [b-ITU-T G.983.1] Appendix II). + +NOTE 3 – As defined in clause 9.2.7.3.1. + +NOTE 4 – Dispersion range is considered to be the most appropriate method of specifying a laser's spectral characteristic. These values are considered to be compatible with the older method of specifying values using maximum –20 dB width, for line rates below 2.5 Gbit/s. + +NOTE 5 – The equivalent maximum –20 dB width value is specified as less than 1 nm. + +NOTE 6 – See [b-ITU-T G Suppl.39], clause 9.4.1 for additional details. + +NOTE 7 – The specified penalty is valid up to a 40 km link distance. + +NOTE 8 – Parameter known in [ITU-T G.984.2] as "Tolerance to the transmitter incident light power". + +NOTE 9 – Parameter known in [ITU-T G.984.2] as "Tolerance to the reflected optical power". + +NOTE 10 – See Annex A for additional spectral requirements that limit harmful crosstalk penalties on the upstream transmissions of coexisting PON systems. Other means to facilitate coexistence are described in [ITU-T G.9805]. + +#### 9.2.7 Transmitter at Old and Oru + +All parameters are specified as follows, and are in accordance with Table 9-3 and Table 9-4. + +##### 9.2.7.1 Source type + +Considering the attenuation/dispersion characteristics of the target fibre channel, feasible transmitter devices include only single-longitudinal mode (SLM) lasers. The indication of a nominal source type in this Recommendation is not a requirement though it is also expected that only SLM lasers will meet all the distance and line rate requirements of the XG-PON systems both for the downstream and upstream links. + +The use of multilongitudinal mode (MLM) lasers is not contemplated in this Recommendation, due to their practical distance/line rate limitations. + +##### 9.2.7.2 Spectral characteristics + +For SLM lasers, the laser is specified as its fibre dispersion range, the range over which the laser characteristics and fibre dispersion result in a defined penalty at a specified fibre distance, under standard operating conditions. Additionally, for control of mode partition noise in SLM systems, a minimum value for the laser side-mode suppression ratio is specified. The actual spectral + +characteristics are limited by the maximum amount of OPP produced with the worst-case optical dispersion in the data channel. + +The use of MLM lasers is not contemplated in this Recommendation. + +##### 9.2.7.3 Mean launched power + +The mean launched power at $O_{Id}$ and $O_{ru}$ 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 all allowances for operation under standard operating conditions, transmitter connector degradation, measurement tolerances and ageing effects. + +In the operating state, the lower figure is the minimum power to be provided and the higher one is the power never to be exceeded. + +NOTE – Measurement of the launched power at the $O_{ru}$ optical interface must take into account the burst nature of the upstream traffic transmitted by the ONUs. + +###### 9.2.7.3.1 Launched optical power without input to the transmitter + +In the upstream direction, the ONU transmitter should ideally launch no power into the fibre in all bursts which are not assigned to that ONU. However, an optical power level less than or equal to the launched power without input to the transmitter is allowed during bursts which are not assigned to that ONU. During the Tx enable bit period the transmit levels are not specified, provided they comply with the PMD Tables 9-3 and 9-4. During the Tx disable bit period immediately following the assigned burst, the maximum launch power level allowed is the zero-level corresponding to the minimum extinction ratio specified in Tables 9-3 and 9-4. + +The specification of the maximum number of Tx enable and Tx disable bit periods is provided in Table 9-3 and Table 9-4. + +The relationship between ONU power levels and burst times is shown in Figure 9-1. + + + +The figure is a line graph showing optical power levels over time for a single burst. The vertical axis is labeled 'Transmit Power' and has two markers: '0 Level' and '1 Level'. The horizontal axis is labeled 'Bit durations'. The burst is divided into five segments by vertical lines and labels above the graph: 'Tx enable', 'Preamble', 'Delimiter', 'Rest of burst', and 'Tx disable'. In the 'Tx enable' segment, a dashed line rises from the 0 level to a peak above the 1 level and then falls. In the 'Preamble' and 'Delimiter' segments, a solid line shows a series of rectangular pulses between the 0 and 1 levels. In the 'Rest of burst' segment, a shaded area represents a constant power level between 0 and 1. In the 'Tx disable' segment, a dashed line falls from the 0 level to a negative value. Below the x-axis, there are two shaded rectangular areas labeled 'Launched optical power without input to the transmitter', one at the beginning and one at the end of the burst. The graph is labeled 'G.987.2(23)\_F9-1' in the bottom right corner. + +Figure 9-1: Relationship between ONU power levels and burst times. The graph shows Transmit Power on the y-axis (0 Level, 1 Level) versus Bit durations on the x-axis. The burst is divided into five segments: Tx enable, Preamble, Delimiter, Rest of burst, and Tx disable. The Tx enable segment shows a dashed line representing power without input. The Preamble and Delimiter segments show a solid line representing the transmitted signal. The Rest of burst segment shows a shaded area representing the transmitted signal. The Tx disable segment shows a dashed line representing power without input. The graph is labeled G.987.2(23)\_F9-1. + +Figure 9-1 – Relationship between ONU power levels and burst times + +##### 9.2.7.4 Minimum extinction ratio + +The extinction ratio (ER) is defined as: + +$$ER = 10 \log_{10} (A/B)$$ + +where $A$ is the average optical power level at the centre of the binary 1 and $B$ is the average optical power level at the centre of the binary 0. + +The ER for the upstream direction burst mode signal is applied from the first bit of the preamble to the last bit of the burst signal, inclusive. + +##### 9.2.7.5 Maximum reflectance of equipment, measured at transmitter wavelength + +Reflections from equipment (ONU/OLT) back to the cable plant are specified by the maximum permissible reflectance of equipment measured at $O_{ld}/O_{ru}$ , in accordance with Table 9-3 and Table 9-4. + +##### 9.2.7.6 Mask of transmitter eye diagram + +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 $O_{ld}/O_{ru}$ . For the purpose of assessing the transmit signal, it is important to consider not only the eye opening, but also the overshoot and undershoot limitations. + +###### 9.2.7.6.1 OLT transmitter + +The parameters specifying the mask of the eye diagram (see Figure 9-2) for the OLT transmitter are shown in Table 9-5. The test set-up for the measurement of the mask of the eye diagram is shown in Figure 9-3. + + + +Figure 9-2: Mask of the eye diagram for OLT transmitter. 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 (mean level of logical '0'), 0.5 (eye center), Y1, Y2, 1 (mean level of logical '1'), and 1+Y3. The horizontal axis represents time from 0 to 1 UI, with mask boundaries at X2 and X3. The mask is a shaded rectangular region between X2 and X3 and between Y1 and Y2. + +G.987.2(16)\_F9-2 + +Figure 9-2 – Mask of the eye diagram for OLT transmitter + +Table 9-5 – Mask of the eye diagram for OLT transmitter – Numeric values + +| | 9.95328 Gbit/s | +|----------------------|----------------| +| $x_3 - x_2$ (Note 1) | 0.2 | +| $y_1$ | 0.25 | +| $y_2$ | 0.75 | +| $y_3$ | 0.25 | +| $y_4$ | 0.25 | + +NOTE 1 – $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. +NOTE 2 – The values are taken from [ITU-T G.959.1], clause 7.2.2.14. + + + +[Test set-up] + +``` + +[Optical transmitter] --> [Attenuator a)] --> [O/E converter fourth-order Thomson filter b)] --> [Waveform monitor] + +``` + +G.987.2(16)\_F9-3 + +a) Attenuator is used if necessary. + +b) Cut-off frequency (3 dB attenuation frequency) of the filter is 0.75 times output nominal bit rate. + +**Figure 9-3 – Test set-up for mask of the eye diagram for OLT transmitter** + +###### 9.2.7.6.2 ONU transmitter + +The parameters specifying the mask of the eye diagram (see Figure 9-4) for the ONU transmitter are shown in Table 9-6. The test set-up for the measurement of the mask of the eye diagram is shown in Figure 9-5. + + + +G.987.2(14)-Amd.1\_F9-4 + +Figure 9-4: Mask of the eye diagram for ONU transmitter. The diagram shows an eye diagram with a rectangular mask. The vertical axis represents normalized voltage from -y4 to 1+y3. The horizontal axis represents time from 0 to 1 UI. The mask is defined by parameters x2, x3, y1, y2, y3, and y4. The mean level of the center of logical '1' is indicated at level 1, and the mean level of the center of logical '0' is indicated at level 0. + +**Figure 9-4 – Mask of the eye diagram for ONU transmitter** + +**Table 9-6 – Mask of the eye diagram for ONU transmitter – Numeric values** + +| | 2.48832 Gbit/s | 9.95328 Gbit/s | +|----------------------|-----------------------|-----------------------| +| $x_3 - x_2$ (Note 1) | 0.2 | 0.2 | +| $y_1, y_3, y_4$ | 0.25 | 0.25 | +| $y_2$ | 0.75 | 0.75 | + +NOTE 1 – Parameters $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. +NOTE 2 – The values are taken from [ITU-T G.957], clause 6.2.5. + + + +[Test set-up] + +``` + +[Optical transmitter] --> [Attenuator a)] --> [O/E converter fourth-order Thomson filter b)] --> [Waveform monitor] + +``` + +G.987.2(16)\_F9-5 + +a) Attenuator is used if necessary. + +b) Cut-off frequency (3 dB attenuation frequency) of the filter is 0.75 times output nominal bit rate. + +**Figure 9-5 – Test set-up for mask of the eye diagram for ONU transmitter** + +The mask of the eye diagram for the upstream direction burst mode signal is applied from the first bit of the preamble to the last bit of the burst signal, inclusive. + +##### **9.2.7.7 Transmitter tolerance to reflected optical power** + +The specified transmitter performance must be met in the presence of the optical reflection level at reference point S specified in Table 9-3 and Table 9-4. + +#### **9.2.8 Optical path between $O_{ld}/O_{ru}$ and $O_{rd}/O_{lu}$** + +##### **9.2.8.1 Attenuation range** + +Four classes of attenuation ranges are specified in clause 6.1. + +Attenuation specifications are assumed to be worst-case values at all wavelengths specified in Table 9-3 and Table 9-4, 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 connector, optical attenuators (if used) or other passive optical devices between points S and R, when provided. + +##### **9.2.8.2 Minimum optical return loss of the cable plant at point R/S, including any connectors** + +Overall minimum optical return loss (ORL) specification at point R/S in the ODN is specified in Table 9-3 and Table 9-4. + +Optionally, minimum ORL specification at point S in the ODN is specified in Note 2 of Table 9-3 and Table 9-4. + +NOTE – The overall reflectance at the S/R point for an ODN model is dominated by the optical connectors at the optical distribution frame (ODF). The maximum reflectance of a single discrete element within [ITU-T G.982] is $-35$ dB. The reflectance from the two ODF connectors leads to a figure of $-32$ dB. However, based on another network model, the overall reflectance may become worse than $-20$ dB. + +##### **9.2.8.3 Maximum discrete reflectance between points S and R** + +All discrete reflectances in the ODN shall be better than $-35$ dB as defined in [ITU-T G.982]. + +##### **9.2.8.4 Dispersion** + +Systems considered limited by dispersion have maximum values of dispersion (ps/nm) specified in Table 9-3 and Table 9-4. These values are consistent with the maximum optical path penalties specified. They take into account the specified transmitter type, and the fibre dispersion coefficient over the operating wavelength range. + +#### **9.2.9 Receiver at $O_{rd}$ and $O_{lu}$** + +All parameters are specified as follows, in accordance with Table 9-3 and Table 9-4. + +##### **9.2.9.1 Receiver sensitivity** + +Receiver sensitivity is defined in [ITU-T G.987]. The values are specified in Table 9-3 and Table 9-4. Receiver sensitivity takes into account power penalties caused by the use of a transmitter under standard operating conditions with worst-case values of ER, pulse rise and fall times, optical return loss (ORL) at point R/S, receiver connector degradation and measurement tolerances. The receiver sensitivity does not include power penalties associated with dispersion, jitter or reflections from the optical path; these effects are specified separately in the allocation of maximum OPP. + +##### 9.2.9.2 Receiver overload + +Receiver overload is defined in [ITU-T G.987]. The values are specified in Table 9-3 and Table 9-4, accordingly. The receiver should have a certain robustness against increased optical power level due to start-up or potential collisions during ranging, for which the BER, specified in Table 9-3 and Table 9-4, is not guaranteed. + +##### 9.2.9.3 Maximum optical path penalty + +Optical path penalty is defined in [ITU-T G.987]. The receiver is required to tolerate an OPP not exceeding the value specified in Table 9-3 and Table 9-4. + +##### 9.2.9.4 Maximum reflectance at R/S, measured at receiver wavelength + +Reflections from equipment (ONU/OLT) back to the cable plant are specified by the maximum permissible reflectance of equipment measured at $O_{rd}$ and $O_{lu}$ . It shall be in accordance with Table 9-3 and Table 9-4. + +##### 9.2.9.5 Differential optical path loss + +Differential optical path loss means the optical path loss difference between the highest and lowest optical path loss in the same ODN. The maximum differential optical path loss is defined in Table 9-3 and Table 9-4. + +##### 9.2.9.6 Clock extraction capability + +NOTE – The clock of the upstream transmission signal is extracted rapidly from several alternating bits in the preamble. The clock extracted from the preamble is maintained at least during reception of the signal from the delimiter through the end of the upstream assigned burst, or is continuously extracted from the signal after the preamble during reception of the assigned burst. + +##### 9.2.9.7 Jitter performance + +This clause deals with jitter requirements for optical interfaces of XG-PON. + +###### 9.2.9.7.1 Jitter transfer + +The jitter transfer specification applies only to the ONU. + +The jitter transfer function is defined as: + +$$jitter\ transfer = 20 \log_{10} \left[ \frac{jitter\ on\ upstream\ signal\ UI}{jitter\ on\ downstream\ signal\ UI} \times \frac{downstream\ bit\ rate}{upstream\ bit\ rate} \right]$$ + +The jitter transfer function of an ONU shall be under the curve given in Figure 9-6, when input sinusoidal jitter up to the mask level in Figure 9-7 is applied, with the parameters specified in this figure for each line rate. + + + +| Upstream line rate (Gbit/s) | $f_L$ (kHz) | $f_C$ (kHz) | $f_H$ (kHz) | P (dB) | +|-----------------------------|-------------|-------------|-------------|--------| +| 2.48832 | 20 | 2000 | 20'000 | 0.1 | + +NOTE – These values are taken from [ITU-T G.783] + +G.987.2(16)\_F9-6 + +Graph of Jitter gain vs Frequency for ONU. The y-axis is Jitter gain (P) and the x-axis is Frequency (f\_L, f\_C, f\_H). The gain is constant at P from f\_L to f\_C, then decreases with a slope of -20 dB/dec until f\_H. + +**Figure 9-6 – Jitter transfer for ONU** + + + +| Downstream line rate (Gbit/s) | $A_3$ (UI) | $A_4$ (UI) | $f_2$ (kHz) | $f_3$ (kHz) | +|-------------------------------|------------|------------|-------------|-------------| +| 9.95328 | 1.5 | 0.15 | 400 | 4000 | + +NOTE – These values are taken from [ITU-T G.783] + +G.987.2(16)\_F9-7 + +Graph of Input jitter amplitude vs Frequency for jitter transfer. The y-axis is Input jitter amplitude (A3, A4) and the x-axis is Frequency (f2, f3). The amplitude is constant at A3 from 0 to f2, then decreases with a slope of -20 dB/dec until f3, where it becomes constant at A4. + +**Figure 9-7 – High-band portion of sinusoidal jitter mask for jitter transfer** + + + +| Line rate (Gbit/s) | $f_r$ [kHz] | $f_0$ [kHz] | $A_1$ [UIp-p] | $A_2$ [UIp-p] | +|--------------------------------------------------------------------------------|-------------|-------------|---------------|---------------| +| 2.48832 | 1000 | 100 | 0.075 | 0.75 | +| 9.95328 | 4000 | 400 | 0.075 | 0.75 | +| NOTE – These values are scaled to 10 Gbit/s from the values in [ITU-T G.984.2] | | | | | + +G.987.2(16)\_F9-8 + +Figure 9-8: Jitter tolerance mask graph and table. The graph shows Input jitter amplitude on the y-axis and Frequency on the x-axis. The mask starts at amplitude A2, stays flat until frequency f0, then slopes down at -20 dB/dec until frequency fr, where it levels off at amplitude A1. The table below provides specific values for these parameters at different line rates. + +**Figure 9-8 – Jitter tolerance mask** + +###### 9.2.9.7.2 Jitter tolerance + +Jitter tolerance is defined as the peak-to-peak amplitude of sinusoidal jitter applied on the input XG-PON signal that causes a 1 dB optical power penalty at the optical equipment. Note that it is a stress test to ensure that no additional penalty is incurred under operating conditions. + +The ONU shall tolerate, as a minimum, the input jitter applied according to the mask in Figure 9-8, with the parameters specified in that figure for the downstream line rate. The OLT should tolerate, as a minimum, the input jitter applied according to the mask in Figure 9-8, with the parameters specified in that figure for the upstream line rate. The jitter tolerance specification for the OLT is informative as it can only be measured in a setting that permits continuous operation of the upstream. + +###### 9.2.9.7.3 Jitter generation + +An ONU shall not generate a peak-to-peak jitter amplitude more than shown in Table 9-7 at a line rate of 2.48832 Gbit/s, with no jitter applied to the downstream input and with a measurement bandwidth as specified in Table 9-7. An OLT shall not generate a peak-to-peak jitter amplitude more than that shown in Table 9-7 at a line rate of 9.95328 Gbit/s, with no jitter applied to its timing reference input and with a measurement bandwidth as specified in Table 9-7. + +**Table 9-7 – Jitter generation requirements for XG-PON** + +| Line rate (Gbit/s) | Measurement band
(−3 dB frequencies)
(Note 1) | | Peak-peak amplitude
(UI)
(Note 2) | +|--------------------|-----------------------------------------------------|------------------------------|-----------------------------------------| +| | High-pass
(kHz) | Low-pass (MHz)
−60 dB/dec | | +| 2.48832 | 5 | 20 | 0.30 | +| | 1000 | 20 | 0.10 | +| 9.95328 | 20 | 80 | 0.30 | +| | 4000 | 80 | 0.10 | + +NOTE 1 – The high-pass and low-pass measurement filter transfer functions are defined in clause 5 of [ITU-T G.825]. + +NOTE 2 – The measurement time and pass/fail criteria are defined in clause 5 of [ITU-T G.825]. + +NOTE 3 – This table comes from [ITU-T G.783]. + +##### **9.2.9.8 Consecutive identical digit (CID) immunity** + +The OLT and the ONU shall have a CID immunity as specified in the series of Table 9-3 and Table 9-4. + +##### **9.2.9.9 Receiver tolerance to reflected power** + +The receiver tolerance to reflected power is the allowable ratio of optical input average power of $O_{rd}$ and $O_{lu}$ to reflected optical average power when multiple reflections are regarded as a noise light at $O_{rd}$ and $O_{lu}$ , respectively. + +The receiver tolerance to reflected power is defined at minimum receiver sensitivity. + +##### **9.2.9.10 Transmission quality and error performance** + +To avoid system down time or failures, the frame structure should be robust in the presence of transmission BER up to the values defined in Table 9-3 and Table 9-4. + +The average BER on individual links across the entire PON system will typically be lower than the values defined in Table 9-3 and Table 9-4. Optical components should provide BER better than the values defined in Table 9-3 and Table 9-4 when conditions allow. + +# **10 X/S tolerance masks** + +## **10.1 X/S tolerance mask for ONU** + +The minimum optical sensitivity of an XG-PON ONU must be met in the presence of interference signals. Interference signals are caused by other services such as G-PON and/or video signals in the enhancement band specified in [ITU-T G.987.1]. To minimize the effect of interference signals, XG-PON ONUs need to isolate them using an appropriate wavelength blocking filter (WBF) and WDM filter. This Recommendation does not specify the isolation characteristics of the WBF and WDM filters directly, but specifies the X/S tolerance of the XG-PON ONU. Here, S is the optical power of the XG-PON signal, and X is that of the interference signal(s). Both are measured at the ONU reference point R/S, corresponding to the ONU reference point $IF_{XGPON}$ specified in [ITU-T G.987.1]. + +The interference signal format for measuring X/S tolerance is a non-return-to-zero (NRZ) pseudo-random code with the same line rate as the XG-PON downstream signal or a lower line rate within the bandwidth of the XG-PON receiver. + +This tolerance can be used to design a variety of WDM configurations at the ONU. It makes no definite assumption about additional services using the enhancement band specified in [ITU-T G.987.1]. Figure 10-1 shows the X/S tolerance mask that should not cause the XG-PON receiver to fail to meet its sensitivity requirements. Implementers need to specify the isolation characteristics of the WBF and WDM filters to obtain enough isolation of the interference signal(s). This allows the XG-PON sensitivity requirement to be met in the presence of this level of interference. The wavelengths and total optical launched power of additional services must fall beneath the mask of Figure 10-1 to allow coexistence with XG-PON. + + + +Figure 10-1: X/S tolerance mask for ONU (Versatile WDM configuration). The graph shows the X/S (dB) power level on the Y-axis against Wavelength (nm) on the X-axis. The X-axis has markers at 1260, 1560, 1575, 1581, 1596, and 1675 nm. A central 'XG-PON band' is defined between 1575 nm and 1581 nm. Two hatched rectangular regions, representing the blocking wavelength range, are shown from 1260 nm to 1560 nm and from 1596 nm to 1675 nm. A dashed horizontal line indicates the power level Y. The text 'G.987.2(16)-Amd.1(17)\_F10-1' is at the bottom right. + +S: Received power of basic band + +X: Maximum total power of additional services received in the blocking wavelength range. + +X/S: In the mask (hatching area) should not cause the XG-PON receiver to fail to meet its sensitivity requirements. + +**Figure 10-1 – X/S tolerance mask for ONU (Versatile WDM configuration)** + +## 10.2 X/S tolerance mask for OLT + +X/S tolerance mask definition of XG-PON OLT is used to enable a variety of WDM implementations at the OLT. This clause specifies the X/S tolerance mask that should ensure the XG-PON OLT receiver will not fail to meet its sensitivity requirements in the presence of coexisting PON signals. This is an optional requirement for an XG-PON OLT but, in order to facilitate smooth evolution to higher speed PON and alleviate the high isolation requirement of coexistence elements (CEx), it is recommended the necessary WBF be implemented. To ensure X/S compliance, implementers need to design the combined isolation characteristics of the WBF and WDM filters to obtain enough overall isolation of the signals in the blocking wavelength range. This allows the XG-PON OLT sensitivity requirement to be met in the presence of this level of interference. + + + +| Class | Y(dB) | +|----------------|-------| +| N1, N2, E1, E2 | -3 | + +Figure 10-2: X/S tolerance mask for XG-PON OLT. The graph shows the X/S (dB) power level on the Y-axis against Wavelength (nm) on the X-axis. The X-axis has markers at 1260, 1280, 1290, and 1675 nm. A 'Basic band' is defined between 1260 nm and 1280 nm. A hatched rectangular region, representing the blocking wavelength range, is shown from 1290 nm to 1675 nm. A dashed horizontal line indicates the power level Y. Below the graph is a table with two columns: 'Class' and 'Y(dB)'. The text 'G.987.2(16)-Amd.2(20)\_F10-2' is at the bottom right. + +S: Received power. + +X: Maximum total power of additional services received in the blocking wavelength range. + +X/S: In the mask (hatching area) should not cause the XG-PON receiver to fail to meet its sensitivity requirements. + +**Figure 10-2 – X/S tolerance mask for XG-PON OLT** + +# 11 Upstream physical layer overhead + +The XG-PON frame structure is described in [ITU-T G.987.3], which is devoted to the specification of the TC layer. However, upstream bursts must be preceded by suitable physical layer overhead, which is used to accommodate several physical processes. Table 11-1 shows the length of the physical layer overhead for the upstream line rate specified in this Recommendation. + +**Table 11-1 – XG-PON upstream physical layer overhead** + +| Upstream line rate | Overhead bits | +|--------------------|---------------| +| 2.48832 Gbit/s | 256 | + +Moreover, Appendix III provides information on the physical processes that have to be performed during the physical layer overhead ( $T_{\text{plo}}$ ) time, and some guidelines on the optimum use of $T_{\text{plo}}$ . + +## Annex A + +## ONU out-of-band power spectral density + +(This annex forms an integral part of this Recommendation.) + +The purpose of this annex is to specify a set of additional requirements on the ONU transmitter which should be applied in multisystem coexistence deployments. These requirements are stricter than those in the base text of this Recommendation. + +The requirements specified in this annex are optional. Implementations of this Recommendation should not be assumed to meet the requirements of this annex. If the implementer declares the support of this annex, the implementation shall meet all the requirements specified herein. + +Coexistence with other PON systems (e.g., ITU-T G.984.x Series, ITU-T G.989.x Series, ITU-T G.9804.3, etc.) on the same ODN is a frequent requirement for PON system deployments. In such cases, light from ONU transmitters of one PON type may fall into the upstream operating wavelength band of a coexisting PON system. If the optical power of this out-of-band (OOB) light is too high, then this may cause harmful crosstalk penalties on the upstream transmissions of the coexisting PON systems. Such problems are exacerbated in PON ODNs where the differential optical loss is high, and the interfering ONU is on a lower loss path. + +To ensure successful operation in PON coexistence use cases, the out-of-band power spectral density (OOB-PSD) must be below a certain level. The OOB-PSD mask for the ONU transmitter at the R/S interface is shown in Figure A.1 and the values are given in Tables A.1 and A.2. To meet the OOB-PSD mask requirement, the ONU PSD remains below the dashed mask line under all operating conditions. The in-band power limit (Y) is the maximum ONU launched power and the points at the ONU operating band edge (Y-SMSR) represent the power limit given by the ONU transmitter side-mode-suppression ratio (SMSR). The out-of-band PSD (X) is the power outside of the ONU operating wavelength band that may fall into coexisting PON upstream operating wavelength bands. The OOB-PSD spectral interval is 0.1 nm according to the industry convention for optical signal-to-noise measurement. + +![Figure A.1: ONU transmitter OOB-PSD mask definition. The graph shows Optical power on the y-axis and Wavelength (nm) on the x-axis, ranging from 1260 to 1650 nm. The mask is defined by a dashed line. The in-band power limit (Y) is a constant power level between wavelengths λ2 and λ3. The out-of-band PSD (X) is a constant power level outside the band [λ2, λ3]. The points at the band edges (Y-SMSR) are indicated by an arrow pointing to the transition at λ3. The wavelengths λ1, λ2, λ3, and λ4 are marked on the x-axis, with λ1 < λ2 < λ3 < λ4. The mask shows a step down from Y to X at λ2 and a step up from X to Y at λ3. The Y-SMSR point is at λ3. The x-axis has a break between 1260 and 1650 nm.](f880daa1cde4b71fcbaff2df81803a65_img.jpg) + +Figure A.1 illustrates the ONU transmitter OOB-PSD mask. The vertical axis represents Optical power, and the horizontal axis represents Wavelength (nm), with markers at 1260 and 1650 nm. The mask is shown as a dashed line. The in-band power limit (Y) is the maximum power level within the operating band. The out-of-band PSD (X) is the power level outside the operating band. The points at the band edges (Y-SMSR) are indicated by an arrow pointing to the transition at $\lambda_3$ . The wavelengths $\lambda_1$ , $\lambda_2$ , $\lambda_3$ , and $\lambda_4$ are marked on the x-axis, with $\lambda_1 < \lambda_2 < \lambda_3 < \lambda_4$ . The mask shows a step down from Y to X at $\lambda_2$ and a step up from X to Y at $\lambda_3$ . The Y-SMSR point is at $\lambda_3$ . The x-axis has a break between 1260 and 1650 nm. The text G.987.2(23)\_FA.1 is present in the bottom right corner of the graph area. + +Figure A.1: ONU transmitter OOB-PSD mask definition. The graph shows Optical power on the y-axis and Wavelength (nm) on the x-axis, ranging from 1260 to 1650 nm. The mask is defined by a dashed line. The in-band power limit (Y) is a constant power level between wavelengths λ2 and λ3. The out-of-band PSD (X) is a constant power level outside the band [λ2, λ3]. The points at the band edges (Y-SMSR) are indicated by an arrow pointing to the transition at λ3. The wavelengths λ1, λ2, λ3, and λ4 are marked on the x-axis, with λ1 < λ2 < λ3 < λ4. The mask shows a step down from Y to X at λ2 and a step up from X to Y at λ3. The Y-SMSR point is at λ3. The x-axis has a break between 1260 and 1650 nm. + +Figure A.1 – ONU transmitter OOB-PSD mask definition + +**Table A.1 –ONU OOB-PSD mask wavelengths** + +| | Wavelength (nm) | +|-------------|------------------------| +| $\lambda_1$ | Not applicable | +| $\lambda_2$ | 1260 | +| $\lambda_3$ | 1280 | +| $\lambda_4$ | 1284 | + +**Table A.2 – ONU OOB-PSD mask values** + +| Mask range | PSD (dBm measured in 0.1 nm) | +|--------------------------------------------|-------------------------------------| +| $1260 \text{ nm} \leq \lambda < \lambda_1$ | Not applicable | +| $\lambda_1 \leq \lambda < \lambda_2$ | Y-SMSR | +| $\lambda_2 \leq \lambda \leq \lambda_3$ | Y | +| $\lambda_3 < \lambda \leq \lambda_4$ | Y-SMSR | +| $\lambda_4 < \lambda \leq 1650 \text{ nm}$ | X= -41.5 dBm | + +Y= Mean launch power maximum as given in the ONU PMD parameter tables +SMSR= Minimum side-mode-suppression ratio as given in the ONU PMD parameter tables. +NOTE – The OOB-PSD mask specification must be met under the full range of ODN conditions including reflections, as specified elsewhere in this Recommendation. +The mask wavelengths define the boundaries of measurement ranges. The entire 0.1 nm measurement interval should lie inside a single range. + +## Appendix I + +## **Examples of wavelength allocation for XG-PON, G-PON and video distribution services** + +(This appendix does not form an integral part of this Recommendation.) + +See Appendix II of [b-ITU-T G.984.5] for a generic consideration of wavelength allocation for XG-PON, G-PON and video distribution services. + +## **Appendix II** + +## **Physical layer measurements required to support optical layer supervision** + +(This appendix does not form an integral part of this Recommendation.) + +See Annex B in [ITU-T G.984.2]. + +## Appendix III + +## Allocation of the physical layer overhead time + +(This appendix does not form an integral part of this Recommendation.) + +The physical layer overhead time ( $T_{plo}$ ) is used to accommodate five physical processes in the PON. These are: laser on/off time, timing drift tolerance, level recovery, clock recovery and start of burst delimitation. The exact division of the physical layer time to all these functions is determined partly by constraint equations and partly by implementation choices. This appendix reviews the constraints that the OLT must comply with, and suggests values for the discretionary values. + +$T_{plo}$ can be divided into three sections with respect to what ONU data pattern is desired. For simplicity, these times can be referred to as the guard time ( $T_g$ ), the preamble time ( $T_p$ ) and the delimiter time ( $T_d$ ). During $T_g$ , the ONU transmit levels are not specified, provided they comply with the PMD Tables 9-3 and 9-4. During the Tx disable bit period immediately following the assigned burst, the maximum launch power level allowed is the zero-level corresponding to the minimum ER specified in Tables 9-3 and 9-4. During $T_p$ , the ONU will transmit a preamble pattern that provides the desired transition density and signal pattern for fast level and clock recovery functions. Lastly, during $T_d$ , the ONU will transmit a special data pattern with optimal autocorrelation properties that enable the OLT to find the beginning of the burst. Table III.2 gives recommended values for $T_g$ , $T_p$ , $T_d$ and $T_{plo}$ . Figure III.1 shows the timing relationship between the various physical layer overhead times. + + + +Figure III.1: Timing relationship between the various physical layer overhead times. The diagram shows the timing sequence for a burst from ONU i to ONU j. The total overhead time T\_plo is divided into T\_u (uncertainty), T\_on (laser on time), T\_p (preamble), and T\_d (delimiter). The guard time T\_g is shown as the time from the end of the previous burst to the start of the preamble. The timing diagram includes labels for T\_off, T\_u, T\_on, T\_g, T\_p, and T\_d. The text 'End of previous burst, ONU i' is on the left and 'Beginning of body, next burst, ONU j' is on the right. The reference G.987.2(16)\_FIII.1 is shown in the bottom right. + +Figure III.1 – Timing relationship between the various physical layer overhead times + +An additional parameter of the control logic on the PON is the total peak-to-peak timing uncertainty ( $T_u$ ). This uncertainty arises from variations of the time of flight caused by the fibre and component variations with temperature and other environmental factors. + +The constraint equations with which the OLT must comply are then: + +$$T_g > T_{on} + T_u \text{ and } T_g > T_{off} + T_u$$ + +These equations can be explained as follows. The first equation makes sure that the following burst's laser on ramp-up does not fall on top of the last burst's data. The second equation makes sure that the last burst's laser off tail-off does not fall on top of the following burst's preamble. + +$T_p$ must be sufficient for the physical layer to recover the signal level (essentially, setting the decision threshold) and the signal clock phase. There are many diverse design approaches to these two problems, each with its own benefits and costs. Some designs are very fast, but require an external trigger signal and produce sub-optimal error performance. Other designs are slower, but do not require a reset signal and produce bit errors that are normally distributed. In addition, each of these designs may have special requirements on the data pattern used for the preamble. Some designs prefer a maximum transition density pattern, while others prefer a pattern with a balance of transitions and controlled runs of identical digits. + +Since the design is up to the OLT implementer, the OLT is able to configure the details of the preamble that is transmitted by the ONU. This is part of the burst profile discussion below. + +$T_d$ must be long enough to provide a robust delimiter function in the face of bit errors. The error resistance of the delimiter depends on the exact implementation of the pattern correlator, but a simple approximate relationship between the number of bits in the delimiter ( $N$ ) and the number of bit errors tolerated ( $E$ ) is: + +$$E = \text{int}(N/4) - 1 \quad (\text{III.1})$$ + +Equation III.1 has been empirically verified by a numerical search of all delimiters of sizes ranging from 8 to 32 bits. This search was performed under the assumption that the preamble pattern was a '1010' repeating pattern, and that the delimiter had an equal number of zeroes and ones. The Hamming distance, $D$ , of the best delimiter from all shifted patterns of itself and the preamble was found to be $D = \text{int}(N/2) - 1$ ; yielding the error tolerance shown. + +Given a certain BER, the probability of a severely errored burst ( $P_{seb}$ ) is given by: + +$$P_{seb} = \binom{N}{E+1} BER^{E+1} \quad (\text{III.2})$$ + +Substituting equation III.1 into equation III.2, the resultant $P_{seb}$ is given by: + +$$P_{seb} = \binom{N}{\text{int}(N/4)} BER^{\text{int}(N/4)} \quad (\text{III.3})$$ + +If the BER equals $10^{-4}$ , the resultant $P_{seb}$ for various delimiter lengths, $N$ , is given in Table III.1. Inspection of this table shows that, in order to effectively suppress this kind of error, the delimiter length must be at least 16 bits long. The choice of delimiter length and pattern is made by the OLT as part of the burst profile. + +**Table III.1 – Probability of a severely errored burst as a function of delimiter length** + +| $N$ | $P_{seb}$ | +|-----|-----------------------| +| 8 | $2.8 \times 10^{-7}$ | +| 12 | $2.2 \times 10^{-10}$ | +| 16 | $1.8 \times 10^{-13}$ | +| 20 | $1.5 \times 10^{-16}$ | +| 24 | $1.3 \times 10^{-19}$ | +| 32 | $1.1 \times 10^{-25}$ | +| 64 | $4.9 \times 10^{-50}$ | + +With these considerations taken into account, the worst case and objective allocations of the physical layer overhead are given in Table III.2. This table also lists the values for the ONU Tx enable time and Tx disable time, and the total physical layer overhead time for reference. The worst-case values are intended to provide a reasonable bound for easy implementation, and the objective values are intended to be the design target for more efficient implementation with optimized components. These values are for a simple ODN without reach extenders. Reach extenders may require their own guard and preamble time allowances, making the total overhead larger. + +**Table III.2 – Recommended allocation of burst mode overhead time for XG-PON OLT functions** + +| | Tx enable | Tx disable | Total time | Guard time | Preamble time | Delimiter time | +|------------------------|------------------|-------------------|-------------------|-------------------|----------------------|-----------------------| +| Worst case (bit times) | 32 | 32 | 2048 | 128 | 1856 | 64 | +| Objective (bit times) | 32 | 32 | 256 | 64 | 160 | 32 | + +In addition to the design dependent aspects of the burst overhead, there can be operationally dependent factors. For example, detecting an ONU's ranging burst is a more difficult problem than receiving an ONU's regular transmission. To consider another example, some ONUs may have higher power and be easier to detect, and therefore do not need forward error correction (FEC). For these reasons, the OLT may request different burst parameters depending on the context. + +The concept of a burst profile captures all the aspects of burst overhead control. A burst profile specifies the preamble pattern and length, the delimiter pattern and length, and whether FEC parity should be sent. The OLT establishes one or more burst profiles, and then requests a particular burst profile for each burst transmission. + +The OLT has considerable latitude in setting up the profiles, because the OLT's burst receiver is sensitive to the profile parameters. Therefore, the OLT should use profiles that ensure adequate response in its burst mode receiver. However, some basic requirements from the ONU side must be met. Namely, the preamble and delimiter patterns should be balanced, and they should have a reasonable transition density. If not, the ONU transmitter driver circuitry may be adversely affected. Also note that the preamble and delimiter patterns could differ in each profile, and this difference could be used by the OLT receiver as an in-band indication of the format of each burst (e.g., FEC active or not). + +The details of distributing the burst profiles and signalling their use are described in [ITU-T G.987.3], the XG-PON XGTC layer. + +## Appendix IV + +## Jitter budget specifications + +(This appendix does not form an integral part of this Recommendation.) + +### IV.1 The concept of jitter budget + +Figure IV.1 describes the overall concept of the jitter specification and shows the place of the jitter budget in it. + + + +The diagram illustrates the jitter budget specification in a network. It is divided into two main parts: Downstream (DS) and Upstream (US) jitter. +**Downstream Jitter:** The OLT TX sends data to the ONU RX at the DS Rate. The jitter tolerance specification at the ONU RX must match the jitter generation of the OLT. A graph on the right shows the 'ONU tolerance' mask, which includes 'OLT generation' and a 'Downstream jitter budget' area. +**Upstream Jitter:** The ONU TX sends data to the OLT RX at the US Rate. The jitter generation specification at the ONU TX is shown. A graph on the right shows the 'Jitter transfer spec. (due to loop timing)' and 'ONU transfer'. +**Combined Tolerance:** A text box states: 'Jitter tolerance spec. has to match the sum of ONU jitter generation and the OLT jitter generation filtered by the ONU jitter transfer'. A graph on the left shows the 'OLT tolerance' mask, which includes 'OLT generation transferred by ONU loop', 'Upstream jitter budget', and 'ONU generation'. +**Reference:** G.987.2(23)\_FIV.1 + +Figure IV.1: The place of the jitter budget in the overall jitter specification. The diagram illustrates the flow of jitter in a network. Top part: OLT TX sends DS Rate to ONU RX. Jitter tolerance spec. has to match generation of OLT. ONU RX sends US Rate to OLT RX. Jitter generation spec. is shown for ONU TX. Bottom part: Jitter tolerance spec. has to match the sum of ONU jitter generation and the OLT jitter generation filtered by the ONU jitter transfer. OLT tolerance is shown. OLT generation transferred by ONU loop is shown. Upstream jitter budget is shown. ONU generation is shown. Right side: ONU tolerance is shown. OLT generation is shown. Downstream jitter budget is shown. Jitter transfer spec. (due to loop timing) is shown. ONU transfer is shown. G.987.2(23)\_FIV.1 is noted. + +**Figure IV.1 – The place of the jitter budget in the overall jitter specification** + +The jitter budget specifies jitter components that are not covered by the low frequency jitter specifications. All jitter components accounted for in the jitter budget are integrated over the frequency domain that starts from the upper corner frequency ( $f_t$ ) of the jitter tolerance mask (see clause 9.2.9.7.2). + +The jitter budget is based on the dual Gaussian jitter model. In this model, the jitter components are classified into deterministic jitter (DJ) and random jitter (RJ). The DJ components are modelled as a bimodal distribution and the RJ components as a Gaussian distribution. In addition, the duty-cycle distortion (DCD), which is a DC component, is included into the DJ specification of the jitter budget. The basic assumptions of the model are as follows: + +- 1) Jitter is represented assuming the DJ has an equiprobable bimodal distribution, and the RJ has a Gaussian distribution. +- 2) All sources of random jitter are assumed independent; therefore, RJ RMS values can be added by squares. +- 3) All sources of DJ are assumed to be correlated (this is a worst-case assumption, meaning that all DJ components are either together at maximum value or together at minimum value, with equal probability for the minimum and the maximum to occur). + +Under these assumptions, the total jitter is defined at each given BER by: + +$$TJ_{@BER} = DJ + RJ_{RMS} \cdot 2 \cdot Q^{-1}(BER)$$ + +where $Q^{-1}(BER)$ is the inverse of the $Q$ function. For a very rigorous definition of jitter methodologies, refer to [b-ISO MJSQ]. + +### IV.2 Definition of test points + +In order to build a consistent jitter budget, test points need to be defined at which the jitter components are to be measured. It is important to notice that between the optical module and the SERDES component (whether it is a stand-alone component connected to the MAC through a parallel interface or whether it is integrated inside the MAC ASIC) there is a non-negligible electrical channel. + +The test points of the jitter budget are defined in Figure IV.2 and Table IV.1. + + + +Figure IV.2: Test points of the jitter budget. The diagram shows two main components: an OLT (Optical Line Terminal) and an ONU (Optical Network Unit) connected by a fiber optic cable. The OLT contains a MAC, a SERDES, and an Optics module. The Optics module contains a Laser driver, a TIA, and a LIA. The ONU contains an Optics module, a Laser driver, a TIA, a LIA, a SERDES, and a MAC. Test points are marked at various locations: TPd and TP8 on the OLT's SERDES output; TPa and TP1 on the OLT's Optics module input; TP7 and TP2 on the OLT's optical output; TP6 and TP3 on the ONU's optical input; TP4 and TPx on the ONU's Optics module output; and TP5 and TPY on the ONU's SERDES output. The fiber optic cable connects the OLT's optical output (TP2) to the ONU's optical input (TP3) via a Splitter. + +G.987.2(16)\_FIV.2 + +Figure IV.2 – Test points of the jitter budget + +Table IV.1 – Description of test points for jitter budget + +| Test Point | Description | +|------------|-------------------------------------------------------------------| +| TPa | Electrical test point at the TX output pins of OLT SERDES | +| TP1 | Electrical test point at the TX input pins of OLT optical module | +| TP2 | Optical test point at output of OLT (downstream) | +| TP3 | Optical test point at input of ONU (downstream) | +| TP4 | Electrical test point at the RX output pins of ONU optical module | +| TPx | Electrical test point at the RX input pins of ONU SERDES | +| TPy | Electrical test point at the TX output pins of ONU SERDES | +| TP5 | Electrical test point at the TX input pins of ONU optical module | +| TP6 | Optical test point at output of ONU (upstream) | + +**Table IV.1 – Description of test points for jitter budget** + +| Test Point | Description | +|------------|-------------------------------------------------------------------| +| TP7 | Optical test point at input of OLT (upstream) | +| TP8 | Electrical test point at the RX output pins of OLT optical module | +| TPd | Electrical test point at the RX input pins of OLT SERDES | + +### IV.3 Jitter budget specification for XG-PON + +The proposed values of the jitter components at the different test points are presented in Table IV.2. + +All jitter values are indicated as peak-to-peak values at the BER that corresponds to the respective test point. Jitter at all test points except TP4, TPx, TP8 and TPd is defined at BER = $10^{-12}$ , which is the target BER of the system and also the default BER used by the test instruments. RJ at the receiver is calculated at a power level equal to the sum of the minimum sensitivity and the maximum OPP, as defined in Table 9-3 for the downstream direction and Table 9-4 for the upstream direction. Jitter at TP4 and TPx is defined at BER = $10^{-3}$ , and jitter at TP8 and TPd is defined at BER= $10^{-4}$ , since the system relies on FEC to reach the system target BER. + +**Table IV.2 – Jitter budget for XG-PON** + +| Downstream jitter budget | | | | | +|------------------------------------------------------------------------------|-----------|-----------|-----------|------------| +| Test point | DJ [Uipp] | RJ [Uipp] | TJ [Uipp] | BER | +| Tpa | 0.10 | 0.14 | 0.24 | $10^{-12}$ | +| TP1 | 0.12 | 0.14 | 0.26 | | +| TP2 | 0.21 | 0.18 | 0.38 | | +| TP3 | 0.26 | 0.18 | 0.43 | | +| TP4 | 0.41 | 0.27 | 0.67 | $10^{-3}$ | +| TPx | 0.50 | 0.27 | 0.77 | | +| Upstream jitter budget | | | | | +| Test point | DJ [Uipp] | RJ [Uipp] | TJ [Uipp] | BER | +| Tpy | 0.07 | 0.09 | 0.17 | $10^{-12}$ | +| TP5 | 0.10 | 0.09 | 0.20 | | +| TP6 | 0.24 | 0.10 | 0.35 | | +| TP7 | 0.24 | 0.10 | 0.35 | | +| TP8 | 0.40 | 0.19 | 0.59 | $10^{-4}$ | +| TPd | 0.43 | 0.19 | 0.62 | | +| NOTE – The values in Table IV.2 are for further study and subject to change. | | | | | + +### IV.4 Jitter measurements for compliance to budget + +A set-up that can be used to measure the jitter components at the test points defined in Table IV.1 and verify their compliance to the values given in Table IV.2 is presented in Figure IV.3. + +The set-up contains an OLT and an ONU. The ONU is configured to transmit in continuous mode and a PRBS31 pattern is recommended. + +If measurement of jitter at optical test points is required, optical splitters have to be added to the set-up to permit connection of the O2E probe. If the measurement is to include the dispersion from the optical fibre, then a 20 km spool has to be added to the set-up. + + + +``` + +graph TD + subgraph OLT + MAC_OLT[MAC] + SERDES_OLT[SERDES] + subgraph Optics_Module_OLT[Optics module] + LIA_OLT[LIA] + TIA_OLT[TIA] + LD_OLT[Laser driver] + PD_OLT[Photodiode] + Laser_OLT[Laser] + end + end + + subgraph ONU + MAC_ONU[MAC] + SERDES_ONU[SERDES] + subgraph Optics_Module_ONU[Optics module] + LD_ONU[Laser driver] + TIA_ONU[TIA] + LIA_ONU[LIA] + PD_ONU[Photodiode] + Laser_ONU[Laser] + end + end + + Clk_Source[Clk source] --> Ref_clk_OLT[Ref_clk] + Clk_Source --> Jitter_Unit[Continuous jitter analyse unit] + Ref_clk_OLT --> SERDES_OLT + MAC_OLT <--> SERDES_OLT + SERDES_OLT --> LD_OLT + SERDES_OLT <-- LIA_OLT + LD_OLT --> Laser_OLT + TIA_OLT --> LIA_OLT + PD_OLT --> TIA_OLT + + Laser_OLT --> TP7 + TP7 --> Attenuator[Optical attenuator] + Attenuator --> TP6 + TP6 --> PD_ONU + + Laser_ONU --> TP3 + TP3 --> TP2 + TP2 --> PD_OLT + + LD_ONU --> Laser_ONU + PD_ONU --> TIA_ONU + TIA_ONU --> LIA_ONU + LIA_ONU --> SERDES_ONU + SERDES_ONU --> LD_ONU + SERDES_ONU <--> MAC_ONU + + TP8 --> Jitter_Unit + + style OLT fill:#fff,stroke:#333,stroke-width:1px + style ONU fill:#fff,stroke:#333,stroke-width:1px + +``` + +The diagram illustrates the measurement setup for jitter budget compliance. It consists of two main components: an Optical Line Terminal (OLT) and an Optical Network Unit (ONU) connected by an optical fiber. The OLT contains a MAC, SERDES, and an Optics module with LIA, TIA, and Laser driver components. Test points TPd, TP8, TP7, TP2, TP1, and TPa are indicated. The ONU contains an Optics module with Laser driver, TIA, and LIA components, SERDES, and MAC. Test points TP5, TP6, TP3, TP4, TPx, and TPy are indicated. A Clk source provides a Ref\_clk signal to a Continuous jitter analyse unit, which also receives a signal from TP8 or any other test point. The ONU is configured for continuous transmission of PRBS31. An optical attenuator is connected to the fiber between the OLT and ONU. + +G.987.2(16)\_FIV.3 + +Figure IV.3 – Measurement set-up for jitter budget compliance. The diagram shows an Optical Line Terminal (OLT) and an Optical Network Unit (ONU) connected by an optical fiber. The OLT contains a MAC, SERDES, Optics module (LIA, TIA, Laser driver), and test points TPd, TP8, TP7, TP2, TP1, and TPa. The ONU contains an Optics module (Laser driver, TIA, LIA), SERDES, MAC, and test points TP5, TP6, TP3, TP4, TPx, and TPY. A Clk source provides a Ref\_clk signal to a Continuous jitter analyse unit, which also receives a signal from TP8 or any other test point. The ONU is configured for continuous transmission of PRBS31. An optical attenuator is connected to the fiber between the OLT and ONU. + +**Figure IV.3 – Measurement set-up for jitter budget compliance** + +# Appendix V + +## Measurement of burst mode acquisition time and burst mode eye opening at OLT + +(This appendix does not form an integral part of this Recommendation.) + +One of the major challenges for the burst mode clock and data recovery (CDR) implementation is the need to cope with the transient effects causing additional eye closure at the beginning of the burst. The burst mode CDR has to acquire the phase information exactly on the preamble portion of the incoming data stream, hence it would be reasonable to require the optical module to preserve signal good quality. The better the performance of the optics, the shorter the preamble required for correct system operation. + +We define the burst mode eye opening as the opening of the eye pattern that is collected starting from an offset X from the beginning of the burst. The burst mode acquisition time is defined as the shortest offset X from the beginning of the burst that will render a compliant eye pattern. A compliant eye pattern means an eye opening that meets the jitter budget and correct logical signal levels. + +A set-up for measuring burst mode acquisition time and burst mode eye opening occurring at the beginning of each burst is presented in Figure V.1. + + + +The diagram illustrates the measurement setup. On the left, a 'SeDes and MAC' block is connected to an 'OLT\_TRX' block. 'TX-Data' is transmitted from the MAC to the TRX, while 'RX-Data' is received from the TRX by the MAC. A 'Differential probe' is connected to the RX-Data line. Below the MAC, a 'Ref clock' is connected. The MAC also sends 'RSSI\_strobe' and 'RX\_RESET' signals to a measurement block at the bottom. This block contains three channels: 'CH0', 'CH1', and 'CH2'. CH0 is a 'Real-time scope, capable of capturing maximum length burst (125 μs)'. CH1 is used to 'Generate eye-pattern for required burst – based on in-scop recovered UI'. CH2 is used to 'Start of eye-pattern sample – is on RSSI\_strobe'. The OLT\_TRX is connected to 'XGPON network fibres and ONTs' via an optical fiber. + +G.987.2(16)\_FV.1 + +Figure V.1: Set-up for measurement of burst mode acquisition time and burst mode eye opening. The diagram shows a SeDes and MAC block connected to an OLT\_TRX block. TX-Data is sent from SeDes and MAC to OLT\_TRX. RX-Data is sent from OLT\_TRX to SeDes and MAC. A Differential probe is connected to the RX-Data line. RSSI\_strobe and RX\_RESET signals are sent from SeDes and MAC to a CH0, CH1, and CH2 block. A Ref clock is connected to the CH0, CH1, and CH2 block. The CH0, CH1, and CH2 block is connected to an XGPON network fibres and ONTs block. The CH0, CH1, and CH2 block contains a list of requirements for the real-time scope. + +**Figure V.1 – Set-up for measurement of burst mode acquisition time and burst mode eye opening** + +The following is a list of recommendations related to measurement of burst mode acquisition time and burst mode eye opening compliance: + +- Use a real time sampling scope capable of 40 GS/s or more and a memory depth that can cover at least 125 μs (5M samples) for capturing the eye pattern. +- In order to separate the eye pattern that corresponds to a single given ONU, the oscilloscope is triggered on RSSI-strobe signal [b-ITU-T G Suppl. 48]. The timing diagram for this signal is presented in Figure V.2. + +- The burst mode eye diagram is built from the data collected during the sampling window defined in Figure V.3. +- The eye pattern is built using a unit interval (UI) based on an average unit interval (UI) calculated from the collected data. +- The differential probe can be placed to perform measurement at either TP8 (module pins) or at TPd (SERDES pins) (see Figure IV.2). +- The pass/fail condition should be a burst mode eye opening in excess of 0.38 UI at TPd and correct logical signal levels. Note that 0.38 UI is equal to $(1 - T_J)$ for test point TPd in Table IV.2. + + + +Figure V.2: Timing diagram showing the relationship between optical signals from three ONUs (ONU1, ONU2, ONU3), RX\_RESET signals, and the RSSI\_strobe signal. The top graph shows optical signal bursts from ONU1, ONU2, and ONU3. The middle graph shows RX\_RESET pulses triggered for each ONU burst. The bottom graph shows the RSSI\_strobe signal, which is a pulse relayed to the measured ONU (ONU2) during its burst. A double-headed arrow labeled 'Measured ONU Signal' indicates the timing window for the measurement on ONU2. The diagram is labeled G.987.2(16)\_FV.2. + +**Figure V.2 – RSSI\_strobe timing relative to selected burst source** + +The test set-up shown in Figure V.1 can be used to determine the burst mode acquisition time of a given set of optics. The eye pattern measurement is repeated for different values of the parameter X (defined in Figure V.3) and the minimum setting of X for which the (horizontal) burst mode eye opening at TPd is better than 0.38 UI determines the burst mode acquisition time of the system. Note that 0.38 UI is equal to $(1 - T_J)$ for test point TPd in Table IV.2. + +The system will perform correctly for settings of the preamble length that are longer than the burst mode acquisition time. + + + +The figure is a timing diagram with four horizontal timelines. + +1. **Optical signal at the input to the OLT TRX**: Shows a green burst followed by a gap labeled 'Guard', then a grey burst labeled 'Preamble ≤ Max-Length' and 'From ONU2'. A long horizontal double-headed arrow above the grey burst is labeled 'Measured ONU signal'. + +2. **OLT-TRX RX electrical signal**: Shows a purple burst, a gap, and then a grey burst labeled 'From ONU2'. A small horizontal double-headed arrow labeled 'X' is positioned between the start of the purple burst and the start of the grey burst. + +3. **RX\_RESET according to TRX-manufacturer Recommendation**: Shows a single rectangular pulse. + +4. **RSSI\_strobe relayed to measured ONU**: Shows a single rectangular pulse. + +Vertical dashed lines indicate timing relationships: + +- A dashed line from the start of the grey burst on the first timeline to the start of the grey burst on the second timeline. + +- A dashed line from the start of the grey burst on the second timeline to the start of the 'Sampled signal for EYE opening measurement' (indicated by a long horizontal double-headed arrow). + +- A dashed line from the end of the 'Sampled signal for EYE opening measurement' to the start of the pulse on the fourth timeline. + +A label 'G.987.2(16)\_FV.3' is located at the bottom right of the diagram. + +Timing diagram showing four signal levels over time: Optical signal at the input to the OLT TRX, OLT-TRX RX electrical signal, RX\_RESET according to TRX-manufacturer Recommendation, and RSSI\_strobe relayed to measured ONU. The diagram illustrates the timing for burst mode acquisition and eye opening measurements, including labels for 'Measured ONU signal', 'Preamble ≤ Max-Length', 'Guard', 'From ONU2', 'X', and 'Sampled signal for EYE opening measurement'. A reference label G.987.2(16)\_FV.3 is present at the bottom right. + +**Figure V.3 – Timing diagram of the sampling window for burst mode acquisition time and burst mode eye opening measurements** + +# Bibliography + +- [b-ITU-T G.983.1] Recommendation ITU-T G.983.1 (2005), *Broadband optical access systems based on passive optical networks (PON)*. +- [b-ITU-T G.984.5] Recommendation ITU-T G.984.5 (2022), *Gigabit-capable passive optical networks (G-PON): Enhancement band*. +- [b-ITU-T G Suppl.39] ITU-T G-series Recommendations – Supplement 39 (2016), *Optical system design and engineering considerations*. +- [b-ITU-T G Suppl. 48] ITU-T G-series Recommendations – Supplement 48 (2010), *10-Gigabit-capable passive optical networks: Interface between media access control with serializer/deserializer and physical medium dependent dublayers*. +- [b-ISO MJSQ] ISO/IEC TR 14165-117:2007, *Information technology – Fibre Channel – Part 117: Methodologies for jitter and signal quality (MJSQ)*. +<
Ch B
Ch C | – | – | + +Table 7-1 and Table 7-3 shall be used in combination. + +Example: + +A node intended for the EU region may use configuration 2 which provides two alternative communication channels. The following RF profiles are available: + +- RF profile 1 at the frequency $f_{\text{EU1}}$ (Ch A) supporting data rate R3 in AL mode only. +- RF profile 2 at the frequency $f_{\text{EU2}}$ (Ch B) supporting data rates R1 and R2 in AL mode only. +- RF profile 3 at the frequency $f_{\text{EU2}}$ (Ch B) supporting data rate R2 in AL and FL mode. + +This imaginary node runs on battery but has to support low-latency communication. Thus, FL mode is preferred. When listening or transmitting to other FL nodes, the node uses RF Profile 3 (Ch B). When sending to AL nodes, the node uses RF Profile 1 (Ch A) or RF Profile 2 (Ch B). + +#### 7.1.2.4 Modulation and encoding + +The PHY shall employ frequency shift keying (FSK) for RF modulation at data rates R1 and R2. The PHY shall employ Gaussian frequency shift keying (GFSK) for RF modulation at data rate R3. + +Manchester code shall be used for data symbol encoding at data rate R1 and non-return-to-zero (NRZ) shall be used for data symbol encoding at data rates R2 and R3. + +The modulation and the coding format are summarized in Table 7-4. + +**Table 7-4 – Modulation and coding format** + +| Data Rate | Modulation | Coding | Frequency offset | Separation | Symbols | +|-----------|----------------|------------|------------------|-------------------|---------| +| R1 | FSK | Manchester | 20 kHz | 40 kHz $\pm 20\%$ | Binary | +| R2 | FSK | NRZ | 0 kHz | 40 kHz $\pm 20\%$ | Binary | +| R3 | GFSK, BT = 0.6 | NRZ | 0 kHz | 58 kHz $\pm 20\%$ | Binary | + +The mapping of NRZ symbols to the physical medium is given in Table 7-5: + +**Table 7-5 – NRZ symbol mapping** + +| Symbol | Frequency | +|--------|-----------------------------------------------------| +| 0 | $f_{\text{center frequency}} + \text{separation}/2$ | +| 1 | $f_{\text{center frequency}} - \text{separation}/2$ | + +The mapping of Manchester symbols to the physical medium is given in Table 7-6: + +**Table 7-6 – Manchester symbol mapping** + +| Symbol | Frequency | +|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Transition from $(f_{\text{center frequency}} + f_{\text{offset}} - \text{separation}/2)$ to $(f_{\text{center frequency}} + f_{\text{offset}} + \text{separation}/2)$ | +| 1 | Transition from $(f_{\text{center frequency}} + f_{\text{offset}} + \text{separation}/2)$ to $(f_{\text{center frequency}} + f_{\text{offset}} - \text{separation}/2)$ | + +Table 7-6 refers to a frequency offset, $f_{\text{offset}}$ . The frequency offset is specified in Table 7-4. + +#### 7.1.2.5 Transmitter (TX) and receiver requirements + +Unless stated otherwise, all RF power measurements, either transmit or receive, shall be made at the antenna connector. The measurements shall be made with equipment that is either matched to the impedance of the antenna connector or corrected for any mismatch. For devices without an antenna connector, the measurements shall be interpreted as effective isotropic radiated power (EIRP) (i.e., a 0 dBi gain antenna), and any radiated measurements shall be corrected to compensate for the antenna gain in the implementation. + +##### 7.1.2.5.1 Transmit frequency error + +Frequency error is defined as the difference between the measured transmitted centre frequency and the actual regional centre frequency. + +The frequency error shall not exceed $\pm 27$ ppm. + +##### 7.1.2.5.2 Transmit power adjustments (conducted) + +The TX output power level shall conform to local regulations. The output power level allowed by local regulations is denoted as "nominal." Actual absolute power levels are out of scope of this Recommendation. + +The TX shall be able to adjust its output power in steps of 2 dB in the range between the nominal transmit power down to (nominal output power – 10 dB). + +The TX shall further be able to reduce its output power to at least (nominal output power – 20 dB). + +##### 7.1.2.5.3 Receiver sensitivity + +To ensure a minimum RF link budget, the receiver shall be capable of receiving a standard test frame at a minimum power level. + +The standard test frame and test conditions shall be as specified in Table 7-7. + +The minimum receiver sensitivity for each data rate shall be as specified in Table 7-8. + +**Table 7-7 – Test conditions** + +| Term | Definition | Conditions | +|------------------------|----------------------------------------------------------|----------------------------------------------------------------------------| +| Standard test frame | PHY frame used for testing sensitivity. | PHY frame with at least four bytes of random payload data. | +| Frame error rate (FER) | Average frame loss. | Average measured over standard test frames. | +| Receiver sensitivity | Threshold input signal power that yields a specific FER. | FER < 1% Power measured at antenna terminals.
Interference not present. | + +**Table 7-8 – Minimum receiver sensitivity** + +| Rate | Minimum receiver sensitivity | +|------|------------------------------| +| R1 | –95 dBm | +| R2 | –92 dBm | +| R3 | –89 dBm | + +##### 7.1.2.5.4 Clear channel assessment + +The PHY shall be able to perform a CCA with a threshold of –80 dBm. If the RF channel is found to be idle, the PHY may transmit its data. + +In a given deployment, a listen before talk (LBT) operation based on CCA shall comply with actual regional RF regulatory requirements, e.g., listening period and threshold. + +##### 7.1.2.5.5 Receiver spurious requirement + +A TRX shall limit its RF emissions when in receiver (RX) mode. Emissions near the centre frequency may affect the ability of other nearby devices to receive weak signals. + +A receiver shall not emit more than –70 dBm within $\pm 1$ MHz from the centre frequency as shown in Figure 7-2. The measurement bandwidth shall be 100 kHz. + + + +Figure 7-2: Receiver spurious limit graph. The y-axis is labeled 'Power' and the x-axis is labeled 'Frequency'. A horizontal dashed line at -70 dBm / 100 kHz represents the limit. A rectangular box spans from f\_z - 1 MHz to f\_z + 1 MHz, with a vertical dashed line at the 'Center frequency, f\_z'. The text 'G.9959(15)\_F7-2' is at the bottom right. + +**Figure 7-2 – Receiver spurious limit** + +##### 7.1.2.5.6 Receiver blocking + +Blocking is a measure of the capability of the receiver to receive the intended modulated signal without experiencing degradation due to the presence of another unwanted input signal. + +A conforming implementation shall be able to pass a blocking test as described below for all data rates. + + + +Figure 7-3: Receiver blocking test definition block diagram. A 'Standard test frame' and a 'Signal generator unwanted signal' are inputs to a 'Combiner'. The output of the combiner is connected to a 'Power meter' and a 'Receiver'. The text 'G.9959(15)\_F7-3' is at the bottom right. + +**Figure 7-3 – Receiver blocking test definition** + +###### Method of measurement: + +- Standard test frames shall be transmitted at the nominal frequency using the modulation specified for the actual data rate. Its power is adjusted down to a power level which is 3 dB higher than the sensitivity level defined in Table 7-8. +- The blocking test signal shall be a carrier transmitted at a specific offset frequency as defined in Table 7-9. The blocking test signal power shall be increased until the receiver experiences an FER that corresponds to the sensitivity level. + +###### Limits: + +**Table 7-9 – Blocking limits** + +| Frequency offset | Limits | +|------------------|---------| +| ±1 MHz | –44 dBm | +| ±2 MHz | –34 dBm | +| ±5 MHz | –27 dBm | +| ±10 MHz | –25 dBm | + +##### 7.1.2.5.7 Receiver saturation + +The receiver saturation power level is the maximum power level, in decibels relative to 1 mW, present at the input of the receiver. A receiver shall meet the FER criterion in Table 7-7 while receiving at an + +input power level greater than or equal to 0 dBm to sustain "zero" distance between two or more devices. + +##### 7.1.2.5.8 TX-to-RX turnaround time + +The TX-to-RX turnaround time shall be measured from the trailing edge of the last transmitted symbol to the leading edge of the first symbol of the received preamble. + +The TX-to-RX turnaround time shall be less than *aPhyTurnaroundTimeTXRX* (see Table 7-27). + +Latency estimations shall be calculated on the 99th percentile of all latency measurements. + +##### 7.1.2.5.9 RX-to-TX turnaround time + +The RX-to-TX turnaround time shall be measured from the trailing edge of the last received symbol to the leading edge of the first transmitted preamble symbol. + +The RX-to-TX turnaround time shall be more than *aPhyTurnaroundTimeRXTX* (see Table 7-27). + +Latency estimations shall be calculated on the 99th percentile of all latency measurements. + +### 7.1.3 PPDU format + +The general PPDU frame structure is outlined in Figure 7-4. The frame format is depicted in the order in which it is transmitted by the PHY, from left to right, where the leftmost bit is transmitted first in time. Bits within each field are numbered from $k - 1$ (leftmost and most significant) down to 0 (rightmost and least significant), where the length of the field is $k$ bits. Bytes within each multi-byte field are numbered from 1 (leftmost and most significant) up to $n - 1$ (rightmost and least significant), where the length of the field is $n$ bytes. Bits within each byte are numbered from 7 (leftmost and most significant) down to 0 (rightmost and least significant). + +#### 7.1.3.1 General PHY frame format + +The PPDU shall be formatted as illustrated in Figure 7-4. + + + +| | | | | | +|--------|-------------------|--------------------------|------|------------------------| +| Bytes: | m | 1 | n | 1 | +| | Preamble sequence | Start of frame delimiter | PSDU | End of frame delimiter | +| | SHR | | MPDU | EHR* | +| | PPDU | | | | + +\*R1 only +G.9959(15)\_F7-4 + +Diagram of PPDU format showing fields: Preamble sequence (m bytes), Start of frame delimiter (1 byte), PSDU (n bytes), and End of frame delimiter (1 byte). These are grouped into SHR, MPDU, and EHR\* fields, which together form the PPDU. A note indicates EHR\* is R1 only. + +Figure 7-4 – PPDU format + +#### 7.1.3.2 Preamble field + +The preamble field allows a receiver to obtain symbol synchronization. The preamble field shall be composed of a sequence of bytes containing the binary pattern "01010101". Figure 7-5 shows the logical bit waveform of the Manchester encoded preamble pattern for data rate R1. + + + +Figure 7-5: Manchester encoded preamble pattern (R1). The diagram shows a waveform for the bit sequence 0, 1, 0, 1, 0, 1, 0, 1, 1. The first eight bits (0, 1, 0, 1, 0, 1, 0, 1) are labeled as the 'Preamble'. The ninth bit is 1. The waveform for Manchester encoding shows a high-to-low transition for '0' and a low-to-high transition for '1'. + +**Figure 7-5 – Manchester encoded preamble pattern (R1)** + +Figure 7-6 shows the logical bit waveform of the NRZ encoded preamble pattern for data rates R2 and R3. + + + +Figure 7-6: NRZ encoded preamble pattern (R2, R3). The diagram shows a waveform for the bit sequence 0, 1, 0, 1, 0, 1, 0, 1, 1. The first eight bits (0, 1, 0, 1, 0, 1, 0, 1) are labeled as the 'Preamble'. The ninth bit is 1. The waveform for NRZ encoding shows a high level for '0' and a low level for '1'. + +**Figure 7-6 – NRZ encoded preamble pattern (R2, R3)** + +The preamble length shall comply with Table 7-10. The values allow a receiver to scan all channels and obtain synchronization at an arbitrary channel during the duration of the preamble. + +**Table 7-10 – Minimum Preamble length** + +| Channel configurations | Rate | Minimum Preamble length in bytes | | | +|------------------------|------|----------------------------------|-----------|------| +| | | Singlecast/broadcast | Multicast | Beam | +| 1 | R1 | 10 | 10 | n/a | +| | R2 | 10 | 20 | 20 | +| | R3 | n/a | n/a | n/a | +| 2 | R1 | 10 | 10 | n/a | +| | R2 | 10 | 20 | 20 | +| | R3 | 40 | 40 | n/a | +| 3 | R1 | n/a | n/a | n/a | +| | R2 | n/a | n/a | n/a | +| | R3 | 24 | 24 | 8 | + +#### 7.1.3.3 Start of frame (SOF) field + +The SOF is an 8-bit field terminating the preamble field and the start of the PSDU. The SOF shall be formatted as the logical bit pattern illustrated in Table 7-11. + +**Table 7-11 – Format of the SOF field** + +| Bit number | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|---|---|---|---|---|---|---|---| +| Value | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | + +#### 7.1.3.4 PSDU field + +The PSDU field has a variable length and carries the data of the PHY frame. + +#### 7.1.3.5 End of frame (EOF) delimiter field + +The EOF delimiter field shall be sent only when transmitting at data rate R1. The field shall carry a sequence of 8 Manchester code violations each denoted E. Each violation, E, shall be a symbol without transition. Refer to Figure 7-7. + + + +Figure 7-7 – EOF delimiter pattern (R1 only). A timing diagram showing Manchester code transitions. The first four bits are 1, 0, 0, 1, labeled 'Data'. The next eight bits are all 'E' (violations), labeled 'End of frame'. The diagram shows the signal level for each bit: 1 is high-to-low, 0 is low-to-high, and E is a constant level (no transition). + +Figure 7-7 – EOF delimiter pattern (R1 only) + +### 7.1.4 PHY service specifications + +The PHY layer shall provide two services, accessed via two SAPs: the PD, accessed via the PHY data SAP (PD-SAP), and the PHY management service, accessed via the PHY layer management entity SAP (PLME-SAP). The PLME is responsible for maintaining a database of managed objects pertaining to the PHY. This database is referred to as the PHY management information base (MIB). Figure 7-8 shows the components and interfaces of the PHY. + + + +Figure 7-8 – PHY reference model. A block diagram showing the PHY layer components. The MAC layer is at the top, connected to the PHY layer via the PD-SAP (PHY data Service Access Point) and the PLME-SAP (PHY layer Management Entity Service Access Point). The PHY layer contains the PLME (PHY layer Management Entity) and the PHY MIB (Management Information Base). The RF-SAP (Radio Frequency Service Access Point) is at the bottom, connected to the PHY layer. + +Figure 7-8 – PHY reference model + +#### 7.1.4.1 PD service + +The PD-SAP supports the transport of MPDUs between peer MAC entities. Table 7-12 lists the primitives supported by the PD-SAP. + +Table 7-12 – PD-SAP primitives + +| PD-SAP primitive | Request | Confirm | Indication | +|------------------|------------------|------------------|------------------| +| PD-DATA | clause 7.1.4.1.1 | clause 7.1.4.1.2 | clause 7.1.4.1.3 | + +##### 7.1.4.1.1 PD-DATA.request + +The PD-DATA.request primitive requests the transfer of an MPDU (i.e., the PSDU) from the MAC entity to the PHY media. + +###### 7.1.4.1.1.1 Semantics of the PD request primitive + +The semantics of the PD-DATA.request primitive shall be as follows: + +``` +PD-DATA.request ( + psduChannel, + psduRate, + psduLength, + psdu +) +``` + +Table 7-13 specifies the parameters for the PD-DATA.request primitive. + +**Table 7-13 – PD-DATA.request parameters** + +| Name | Type | Valid range | Description | +|-------------|-------------|-------------------------------------------------------------------------------------|-----------------------------| +| psduChannel | Enumeration | Channel A, B, C according to the applied RF profile (see Tables 7-1 and 7-3) | Channel to use | +| psduRate | Enumeration | Data rate R1, R2, R3 according to the applied RF profile (see Tables 7-1 and 7-3) | Data rate to use | +| psduLength | Byte | $\leq aPhyMaxFrameSizeRx$ , where Rx is R1, R2, or R3 depending on actual data rate | Number of bytes to transmit | +| psdu | Byte Array | – | PSDU to transmit | + +###### 7.1.4.1.1.2 When generated + +The PD-DATA.request primitive is generated by the MAC entity and issued to the PHY entity to request the transmission of an MPDU. + +###### 7.1.4.1.1.3 Effects on receipt + +The receipt of the PD-DATA.request primitive by the PHY entity shall cause the transmission of the supplied PSDU. Provided the TX is enabled (TX\_ON mode), the PHY shall construct a PPDU, containing the supplied PSDU, and then transmit the PPDU. When the PHY entity has completed the transmission, it shall issue the PD-DATA.confirm primitive with a status of SUCCESS. + +If the PD-DATA.request primitive is received while the receiver is enabled (RX\_ON mode) or if the TRX is disabled (TRX\_OFF mode), the PHY entity shall issue the PD-DATA.confirm primitive with a status of RX\_ON or TRX\_OFF, respectively. + +##### 7.1.4.1.2 PD-DATA.confirm + +The PD-DATA.confirm primitive confirms the end of the transmission of a PSDU from the MAC entity to the physical media. + +###### 7.1.4.1.2.1 Semantics of the PD confirm primitive + +The semantics of the PD-DATA.confirm primitive shall be as follows: + +``` +PD-DATA.confirm ( + status +) +``` + +Table 7-14 specifies the parameters for the PD-DATA.confirm primitive. + +**Table 7-14 – PD-DATA.confirm parameters** + +| Name | Type | Valid range | Description | +|--------|-------------|-------------------------------|---------------------------------------------------------------------------------------------| +| status | Enumeration | SUCCESS,
RX_ON,
TRX_OFF | Transmission was successful
Error: Currently receiving
Error: Transmitter is disabled | + +###### **7.1.4.1.2.2 When generated** + +The PD-DATA.confirm primitive is generated by the PHY entity and issued to the MAC entity in response to a PD-DATA.request primitive. The PD-DATA.confirm primitive shall return a status of either SUCCESS, indicating that the transmit request was successful, or an error code of RX\_ON or TRX\_OFF. + +###### **7.1.4.1.2.3 Effects on receipt** + +The PD-DATA.confirm primitive allows the MAC entity to take proper action when the transmission has been completed. + +##### **7.1.4.1.3 PD-DATA.indication** + +The PD-DATA.indication primitive indicates the transfer of a PSDU from the PHY to the local MAC entity. + +###### **7.1.4.1.3.1 Semantics of the PD indication primitive** + +The semantics of the PD-DATA.indication primitive shall be as follows: + +``` +PD-DATA.indication ( + psduByte +) +``` + +Table 7-15 specifies the parameters for the PD-DATA.indication primitive. + +**Table 7-15 – PD-DATA.indication parameters** + +| Name | Type | Valid range | Description | +|----------|------|-------------|-------------------------------------------------| +| psduByte | Byte | – | One byte of the PSDU received by the PHY entity | + +###### **7.1.4.1.3.2 When generated** + +The PD-DATA.indication primitive is generated by the PHY entity and issued to the MAC entity to transfer one received PSDU byte. + +###### **7.1.4.1.3.3 Effect on receipt** + +On receipt of the PD-DATA.indication primitive, the MAC entity is notified of the arrival of MPDU data. The MAC layer shall monitor incoming bytes until a complete MPDU has been received. The MAC layer shall use the MPDU Length field to determine the length of the MPDU. The MAC layer shall verify the frame check sequence (FCS) before issuing an MD-DATA.indication to higher layers. + +#### **7.1.4.2 PHY management service** + +The PLME-SAP allows the transport of management commands between the MLME and the PLME. Table 7-16 lists the primitives supported by the PLME-SAP. + +**Table 7-16 – PLME-SAP primitives** + +| PLME-SAP Primitive | Request | Confirm | Indication | Response | +|---------------------------|------------------|------------------|-------------------|-----------------| +| PLME-SOF | – | – | clause 7.1.4.2.1 | – | +| PLME-GET-CCA | clause 7.1.4.2.2 | clause 7.1.4.2.3 | – | – | +| PLME-GET | clause 7.1.4.2.4 | clause 7.1.4.2.5 | – | – | +| PLME-SET-TRX-MODE | clause 7.1.4.2.6 | clause 7.1.4.2.7 | – | – | +| PLME-SET | clause 7.1.4.2.8 | clause 7.1.4.2.9 | – | – | + +##### 7.1.4.2.1 PLME-SOF.indication + +The PLME-SOF.indication primitive indicates the reception of a SOF delimiter from the PHY to the MAC entity. + +###### 7.1.4.2.1.1 Semantics for the service primitive + +The semantics of the PLME-SOF.indication primitive shall be as follows: + +``` +PLME-SOF.indication ( + psduChannel, + psduRate +) +``` + +Table 7-17 specifies the parameters for the PD-DATA.indication primitive. + +**Table 7-17 – PLME-SOF.indication parameters** + +| Name | Type | Valid range | Description | +|-------------|-------------|----------------------|------------------------------------------| +| psduChannel | Enumeration | Channel A, B, C | Channel from which the PSDU was received | +| psduRate | Enumeration | Data rate R1, R2, R3 | Data rate of the received PSDU | + +###### 7.1.4.2.1.2 When generated + +The PLME-SOF.indication primitive is generated by the PLME and issued to the MLME whenever a SOF delimiter is detected by the PHY. + +###### 7.1.4.2.1.3 Effect on receipt + +The MAC entity is notified of the reception of a SOF delimiter. This information may be used by the MAC entity for preparing frame reception and inhibiting transmissions. + +##### 7.1.4.2.2 PLME-GET-CCA.request + +The PLME-GET-CCA.request primitive requests a CCA for a specified channel. + +###### 7.1.4.2.2.1 Semantics for the service primitive + +The semantics of the PLME-GET-CCA.request primitive shall be as follows: + +``` +PLME-GET-CCA.request ( + channel +) +``` + +Table 7-18 specifies the parameters for the PLME-GET-CCA.request primitive. + +**Table 7-18 – PLME-GET-CCA.request parameters** + +| Name | Type | Valid range | Description | +|---------|-------------|---------------------------------------------------------------------------------|----------------------------------------------------------| +| Channel | Enumeration | Channel A, B, or C according to the applied RF profile (see Tables 7-1 and 7-2) | The physical channel on which the CCA is to be performed | + +###### **7.1.4.2.2.2 When generated** + +The PLME-GET-CCA.request primitive is generated by the MLME and issued to the PLME to query the availability of the specified channel. + +###### **7.1.4.2.2.3 Effect on receipt** + +On receipt of the PLME-GET-CCA.request primitive, the PLME should perform a CCA for the specified channel. When the operation is completed, the PLME shall issue a PLME-GET-CCA.confirm advertising the status. + +##### **7.1.4.2.3 PLME-GET-CCA.confirm** + +The PLME-GET-CCA.confirm primitive reports the result of a CCA request. + +###### **7.1.4.2.3.1 Semantics for the service primitive** + +The semantics of the PLME-GET-CCA.confirm primitive shall be as follows: + +``` +PLME-GET-CCA.confirm ( + status +) +``` + +Table 7-19 specifies the parameters for the PLME-GET-CCA.confirm primitive. + +**Table 7-19 – PLME-GET-CCA.confirm parameters** + +| Name | Type | Valid range | Description | +|--------|-------------|--------------------------------------------|----------------------------------------------------------------------------------------------------| +| status | Enumeration | CCA_CLEAR,
CCA_NOT_CLEAR,
CCA_RX_OFF | Channel is ready for transmission
Channel is not ready for transmission
Receiver is disabled | + +###### **7.1.4.2.3.2 When generated** + +The PLME-GET-CCA.confirm primitive shall be generated by the PLME in response to a PLME-GET-CCA.request primitive. The PLME-GET-CCA.confirm primitive may return the status of values CCA\_CLEAR, CCA\_NOT\_CLEAR or CCA\_RX\_OFF. The CCA\_RX\_OFF status shall be returned if the TRX is not in RX mode (and thus, unable to perform a CCA). + +###### **7.1.4.2.3.3 Effect on receipt** + +The MLME is notified of the result of the CCA operation. This information may be used by the MAC entity for channel availability evaluation or for deciding whether to transmit now. + +##### **7.1.4.2.4 PLME-GET.request** + +The PLME-GET.request primitive requests the value of the specified PHY MIB attribute. + +###### **7.1.4.2.4.1 Semantics for the service primitive** + +The semantics of the PLME-GET.request primitive shall be as follows: + +``` + +PLME-GET.request ( + PhyMibAttribute +) + +``` + +Table 7-20 specifies the parameters for the PLME-GET.request primitive. + +**Table 7-20 – PLME-GET.request parameters** + +| Name | Type | Valid range | Description | +|-----------------|-------------|----------------|-------------------------------------| +| PhyMibAttribute | Enumeration | See Table 7-28 | Identifier of the PHY MIB attribute | + +###### 7.1.4.2.4.2 When generated + +The PLME-GET.request primitive shall be generated by the MLME and issued to the PLME to request information from the PHY MIB. + +###### 7.1.4.2.4.3 Effect on receipt + +On receipt of the PLME-GET.request primitive, the PLME should retrieve the value of the specified PHY MIB attribute. + +##### 7.1.4.2.5 PLME-GET.confirm + +The PLME-GET.confirm primitive reports the result of a PHY MIB attribute request. + +###### 7.1.4.2.5.1 Semantics for the service primitive + +The semantics of the PLME-GET.confirm primitive shall be as follows: + +``` + +PLME-GET.confirm ( + status, + PhyMibAttribute, + PhyMibAttributeValue +) + +``` + +Table 7-21 specifies the parameters for the PLME-GET.confirm primitive. + +**Table 7-21 – PLME-GET.confirm parameters** + +| Name | Type | Valid range | Description | +|----------------------|-------------|-----------------------------------|----------------------------------------------------| +| status | Enumeration | SUCCESS,
UNSUPPORTED_ATTRIBUTE | MIB value is available
MIB value does not exist | +| PhyMibAttribute | Enumeration | Refer to Table 7-28 | Identifier of the PHY MIB attribute | +| PhyMibAttributeValue | Various | Attribute specific | Value of the specified PHY MIB attribute | + +###### 7.1.4.2.5.2 When generated + +The PLME-GET.confirm primitive shall be generated by the PLME in response to a PLME-GET.request primitive. + +If a non-existent PHY MIB attribute is requested, the PLME shall issue the PLME-GET.confirm primitive with a status of UNSUPPORTED\_ATTRIBUTE. + +If the requested PHY MIB attribute exists, the PLME shall issue the PLME-GET.confirm primitive with a status of SUCCESS as well as the MIB attribute identifier and its value. + +###### 7.1.4.2.5.3 Effect on receipt + +On receipt of the PLME-GET.confirm primitive, the MLME shall be notified of the result of the PHY MIB attribute request. If the request was successful, the MLME may use the returned MIB attribute value. + +##### 7.1.4.2.6 PLME-SET-TRX-MODE.request + +The PLME-SET-TRX-MODE.request primitive requests that the PHY entity changes the operating mode of the TRX. The TRX may be set to one of the modes outlined in Table 7-22. + +###### 7.1.4.2.6.1 Semantics for the service primitive + +The semantics of the PLME-SET-TRX-MODE.request primitive shall be as follows: + +PLME-SET-TRX-MODE.request ( +mode +) + +Table 7-22 specifies the parameters for the PLME-SET-TRX-MODE.request primitive. + +**Table 7-22 – PLME-SET-TRX-MODE.request parameters** + +| Name | Type | Valid values | Description | +|------|-------------|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Mode | Enumeration | RX_ON,
TRX_OFF,
FORCE_TRX_OFF,
TX_ON | Enable receiver if possible
Disable receiver and transmitter if possible
Force receiver and transmitter off
Enable transmitter if possible | + +###### 7.1.4.2.6.2 When generated + +The PLME-SET-TRX-MODE.request primitive may be generated by the MLME and issued to the PLME to change the operational mode of the TRX. + +###### 7.1.4.2.6.3 Effect on receipt + +On receipt of the PLME-SET-TRX-MODE.request primitive, the PHY should change the TRX operation mode. + +If the PHY is busy receiving or transmitting, the PHY shall ignore the mode request. + +If this primitive is issued with FORCE\_TRX\_OFF, the PHY shall set the TRX mode to TRX\_OFF irrespective of the current mode. + +##### 7.1.4.2.7 PLME-SET-TRX-MODE.confirm + +The PLME-SET-TRX-MODE.confirm primitive shall report the operating mode of the TRX in response to a PLME-SET-TRX-MODE.request. + +If the TRX operation mode is changed, the PHY shall issue the PLME-SET-TRX-MODE.confirm primitive with a status of SUCCESS. + +If the TRX is requested to change to the current operation mode, the PHY shall issue the PLME-SET-TRX-MODE.confirm primitive with a status advertising the current mode, i.e., RX\_ON, TRX\_OFF, or TX\_ON. + +If the TRX is requested to change to the RX\_ON or TRX\_OFF mode and the PHY is busy transmitting, the PHY shall issue the PLME-SET-TRX-MODE.confirm primitive with the status BUSY\_TX. + +If the TRX is requested to change to the TX\_ON or TRX\_OFF mode and the PHY is busy receiving, the PHY shall issue the PLME-SET-TRX-MODE.confirm primitive with the status BUSY\_RX. + +###### 7.1.4.2.7.1 Semantics for the service primitive + +The semantics of the PLME-SET-TRX-MODE.confirm primitive shall be as follows: + +PLME-SET-TRX-MODE.confirm ( +status +) + +Table 7-23 specifies the parameters for the PLME-SET-TRX-MODE.confirm primitive. + +**Table 7-23 – PLME-SET-TRX-MODE.confirm parameters** + +| Name | Type | Valid range | Description | +|--------|-------------|-----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| status | Enumeration | SUCCESS,
RX_ON,
TRX_OFF,
TX_ON,
BUSY_RX,
BUSY_TX | Change request was successful
Receiver is already enabled
Receiver and TX are disabled
TX is already enabled
Receiver is enabled and busy
TX is enabled and busy | + +###### 7.1.4.2.7.2 When generated + +The PLME-SET-TRX-MODE.confirm primitive is generated by the PLME and issued to the MLME. + +###### 7.1.4.2.7.3 Effect on receipt + +The MLME is notified of the operating mode of the TRX. + +The PLME-SET-TRX-MODE.confirm primitive may advertise the status BUSY\_RX or BUSY\_TX. This indicates that the request for a new operation mode was ignored. + +##### 7.1.4.2.8 PLME-SET.request + +The PLME-SET.request primitive may be issued to request that the specified PHY MIB attribute is set to the specified value. + +###### 7.1.4.2.8.1 Semantics for the service primitive + +The semantics of the PLME-SET.request primitive shall be as follows: + +PLME-SET.request ( +PhyMibAttribute, +PhyMibAttributeValue +) + +Table 7-24 specifies the parameters for the PLME-SET.request primitive. + +**Table 7-24 – PLME-SET.request parameters** + +| Name | Type | Valid range | Description | +|----------------------|-------------|--------------------|-------------------------------------| +| PhyMibAttribute | Enumeration | See clause 7.1.5.2 | Identifier of the PHY MIB attribute | +| PhyMibAttributeValue | Various | Attribute specific | Value of the PHY MIB attribute | + +###### 7.1.4.2.8.2 When generated + +The PLME-SET.request primitive is generated by the MLME and issued to the PLME to set the specified PHY MIB attribute. + +###### 7.1.4.2.8.3 Effect on receipt + +On receipt of the PLME-SET.request primitive, the PLME should set the specified PHY MIB attribute to the specified value. + +If a non-existent PHY MIB attribute is specified, the PLME shall not change any MIB attribute. + +If the specified value is invalid for the specified PHY MIB attribute, the PLME shall not change the PHY MIB attribute value. + +If the specified PHY MIB attribute is changed, the change should take effect immediately. + +##### 7.1.4.2.9 PLME-SET.confirm + +The PLME-SET.confirm primitive shall report the result of a requested PHY MIB attribute change. + +###### 7.1.4.2.9.1 Semantics for the service primitive + +The semantics of the PLME-SET.confirm primitive shall be as follows: + +``` +PLME-SET.confirm ( + status, + PhyMibAttribute +) +``` + +Table 7-25 specifies the parameters for the PLME-SET.confirm primitive. + +**Table 7-25 – PLME-SET.confirm parameters** + +| Name | Type | Valid range | Description | +|-----------------|-------------|---------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| status | Enumeration | SUCCESS,
UNSUPPORTED_ATTRIBUTE,
INVALID_PARAMETER | The MIB parameter was set
The MIB parameter does not exist
Invalid value for this MIB parameter | +| PhyMibAttribute | Enumeration | Refer to Table 7-28 | The identifier of the PHY MIB attribute | + +###### 7.1.4.2.9.2 When generated + +The PLME-SET.confirm primitive shall be generated by the PLME and issued to the MLME in response to a PLME-SET.request primitive. + +If a non-existent PHY MIB attribute is specified, the PLME shall advertise a status of UNSUPPORTED\_ATTRIBUTE. + +If the specified value is invalid for the specified PHY MIB attribute, the PLME shall advertise a status of INVALID\_PARAMETER. + +If the specified PHY MIB attribute is updated, the PLME shall advertise a status of SUCCESS. + +###### 7.1.4.2.9.3 Effect on receipt + +The MLME is notified of the result of the PHY MIB attribute change request. The MLME should verify that the status parameter advertises the status value SUCCESS. Refer to Table 7-25. + +#### 7.1.4.3 PHY enumerations description + +Table 7-26 shows PHY enumeration values defined for the PHY layer. + +**Table 7-26 – PHY enumerations description** + +| Enumeration | Description | +|-----------------------|-----------------------------------------------------------------------------------| +| BUSY | CCA operation detected a busy channel | +| BUSY_RX | TRX is receiving and cannot change its mode (unless forced) | +| BUSY_TX | TRX is transmitting and cannot change its mode (unless forced) | +| CCA_CLEAR | CCA operation detected a clear channel | +| FORCE_TRX_OFF | TRX shall be switched off; even if it is currently receiving or transmitting data | +| INVALID_PARAMETER | The specified parameter is out of range for the actual MIB attribute | +| CCA_NO_CLEAR | CCA operation detected a busy channel | +| RX_ON | Receiver is enabled (used for command as well as status) | +| CCA_RX_OFF | CCA request failed: The receiver is disabled | +| SUCCESS | Operation was successful | +| TRX_OFF | Command or Status indicating that the TRX is disabled | +| TX_ON | Command or Status indicating that the TX is enabled | +| UNSUPPORTED_ATTRIBUTE | The specified MIB attribute is not supported | + +### **7.1.5 PHY constants and MIB attributes** + +This clause specifies the constants and attributes relating to the PHY layer. + +#### **7.1.5.1 PHY constants** + +The PHY shall comply with the constants defined in Table 7-27. + +**Table 7-27 – PHY constants** + +| Constants | Description | Value | +|---------------------------------|----------------------------------------------------------|-----------| +| PacketaPhyMaxFrameSizeR1 | Maximum PSDU size for data rate R1 | 64 bytes | +| aPhyMaxFrameSizeR2 | Maximum PSDU size for data rate R2 | 64 bytes | +| aPhyMaxFrameSizeR3 | Maximum PSDU size for data rate R3 | 170 bytes | +| aPhyTurnaroundTimeTXRX | TX-to-RX maximum turnaround time (see clause 7.1.2.5.8). | 1 ms | +| aPhyTurnaroundTimerRXTX | RX-to-TX minimum turnaround time (see clause 7.1.2.5.9). | 1 ms | + +#### **7.1.5.2 PHY MIB attributes** + +The PHY (MIB) comprises the attributes required to manage the PHY. Each of these attributes may be read or written using the PLME-GET.request and PLME-SET.request primitives, respectively. The attributes contained in the PHY MIB are presented in Table 7-28. + +**Table 7-28 – PHY MIB attributes** + +| Attribute | Type | Range | Description | +|----------------------------|-------------|----------------------------------------------------------|-------------------------------| +| phyCurrentTxChannel | Enumeration | A, B, C
(see Table 7-3) | TX channel to use | +| phyMapChannelA | Enumeration | Available RF profiles
(see Table 7-1) | Apply RF profile to channel A | +| phyMapChannelB | Enumeration | Available RF profiles
(see Table 7-1) | Apply RF profile to channel B | +| phyMapChannelC | Enumeration | Available RF profiles
(see Table 7-1) | Apply RF profile to channel C | +| phyTransmitPower | Enumeration | Valid output power levels
(refer to clause 7.1.2.5.2) | Transmit power to use | + +# 8 MAC layer specification + +## 8.1 MAC specifications of the 'sub 1 GHz' TRXs + +### 8.1.1 General + +The MAC layer defines a half duplex protocol for acknowledged wireless communication in a low-cost control network. The MAC layer targets "soft" real-time applications which are not time critical in nature. The MAC layer supports on-demand communication to battery operated nodes. + +MAC Protocol Data Units (MPDU) carry one small header in order to conserve bandwidth. While presented as one header, a few fields are used by higher layers. These fields are carried transparently and ignored by the MAC layer. + +#### 8.1.1.1 Features of the MAC layer + +The features of the MAC layer are channel access, frame validation, acknowledged frame delivery, and retransmission. + +The MAC is responsible for handling the following: + +- domain identification (ID) +- node ID +- collision avoidance algorithm +- backoff algorithm +- automatic retransmission in case of transmission errors +- support for battery operation + +The MAC layer provides two services: the MAC data (MD) service, accessed through the MAC layer data service access point (MD-SAP) and the MAC management service interfacing with the MAC layer management entity service access point (MLME-SAP). The MD service enables reliable transmission and reception of MPDUs across the PD service. + +Constants and attributes that are specified and maintained by the MAC are written in the text of this clause in *italics*. Constants have a general prefix of "aMac", e.g., *aMacMaxMSDUSizeR1*, and are listed in Tables 8-18 and 8-19. Attributes have a general prefix of "mac", e.g., *macHomeID*, and are listed in Table 8-20. + +#### 8.1.1.2 Bootstrapping + +A unique 32-bit identifier called the HomeID is used to identify individual domains. + +NodeIDs are unique within a given domain. A NodeID is an 8-bit short address. A primary node hands out the HomeID and unique NodeIDs to all other nodes included in the domain. + +#### 8.1.1.3 Concept of service primitives + +This clause provides a brief overview of the concept of service primitives (operations). Refer to [b-ITU-T X.210] for more detailed information. + +The services of a layer are the capabilities it offers to the user in the next higher layer or sublayer by building its functions on the services of the next lower layer. This concept is illustrated in Figure 8-1, showing the service hierarchy and the relationship of the two correspondent N-users and their associated N-layer (or sublayer) peer protocol entities. + + + +The diagram shows three vertical lines representing entities over time, indicated by a downward arrow on the left labeled 'Time'. The left line is 'Service user (N-user)', the middle line is 'Service provider (N-layer)', and the right line is another 'Service user (N-user)'. A solid arrow labeled 'Request' points from the left N-user to the N-layer. A dashed arrow labeled 'Indication' points from the N-layer to the right N-user. A solid arrow labeled 'Response' points from the right N-user to the N-layer. A dashed arrow labeled 'Confirm' points from the N-layer to the left N-user. The text 'G.9959(15)\_F8-1' is in the bottom right corner. + +Diagram illustrating service primitives between two N-users and an N-layer service provider. + +**Figure 8-1 – Service primitives** + +The services are specified by describing the information flow between the N-user and the N-layer. This information flow is modelled by discrete, instantaneous events, which characterize the provision of a service. Each event consists of passing a service primitive from one layer to the other through a SAP associated with an N-user. Service primitives convey the required information by providing a particular service. These service primitives are an abstraction because they specify only the provided service rather than the means by which it is provided. This definition is independent of any other interface implementation. + +Services are specified by describing the service primitives and parameters that characterize it. A service may have one or more related primitives that constitute the activity that is related to that particular service. Each service primitive may have zero or more parameters that convey the information required to provide the service. + +A primitive can be one of four generic types: + +- Request: the request primitive is passed from the N-user to the N-layer to request that a service is initiated. +- Indication: the indication primitive is passed from the N-layer to the N-user to indicate an internal N-layer event that is significant to the N-user. This event may be logically related to a remote service request, or it may be caused by an N-layer internal event. +- Response: the response primitive is passed from the N-user to the N-layer to complete a procedure previously invoked by an indication primitive. +- Confirm: the confirm primitive is passed from the N-layer to the N-user to convey the results of one or more associated previous service requests. + +#### 8.1.1.4 Functional overview + +The MAC features of an ITU-T G.9959 network include data transfer model, frame structure, robustness and power consumption. + +##### 8.1.1.4.1 MPDU formats + +A number of MPDU formats are defined. + +Figure 8-2 shows the structure of the general MPDU. The MSDU contains the payload data from higher layers. The MSDU is prepended with a MAC header (MHR) and appended with a MAC footer (MFR). The MHR, MSDU, and MFR together constitute the MPDU. + + + +The diagram illustrates the structure of the General MPDU across two layers: MAC and PHY. The MAC layer is divided into three main components: MAC header (MHR), MAC data payload (MSDU), and FCS (MFR). The PHY layer is divided into PHY header, PHY data payload (PSDU), and End of frame delimiter. The MPDU is shown as a combination of the MHR, MSDU, and MFR. The PPDUs are shown as a single block at the bottom. The diagram includes labels for 'n' and '1/2' at the top, and 'G.9959(15)\_F8-2' at the bottom right. + +Diagram of the General MPDU structure showing the relationship between MAC and PHY layers. The MAC layer contains the MAC header (MHR), MAC data payload (MSDU), and FCS (MFR). The PHY layer contains the PHY header, PHY data payload (PSDU), and End of frame delimiter. The MPDU is the combination of MHR, MSDU, and MFR. The PPDUs are shown as a single block at the bottom. The diagram includes labels for 'n' and '1/2' at the top, and 'G.9959(15)\_F8-2' at the bottom right. + +**Figure 8-2 – General MPDU structure** + +The MPDU is passed to the PHY layer as a PSDU. + +###### 8.1.1.4.1.1 Singlecast MPDU + +The singlecast MPDU uses the general frame structure (Figure 8-2). + +###### 8.1.1.4.1.2 Acknowledgement (ACK) MPDU + +The ACK MPDU uses the general MPDU structure (Figure 8-2). The MSDU may have a length of zero bytes when used for acknowledgement. + +###### 8.1.1.4.1.3 Multicast MPDU + +A multicast header explicitly identifies each target node via a dedicated multicast addressing bitmask. + +##### 8.1.1.4.2 Network robustness + +The ITU-T G.9959 MAC layer employs various mechanisms to ensure robustness in data transmission. These mechanisms of the MAC layer are backoff algorithm, frame ACK, data verification, and frame retransmission. + +###### 8.1.1.4.2.1 CCA + +A node shall query the availability of the channel from the PHY layer before transmitting. If the channel is found to be idle, the node may transmit its data. If the channel is found busy, the node shall wait for idle channel before transmitting. + +###### 8.1.1.4.2.2 ACK + +A successful reception and validation of an MPDU may be confirmed with an ACK MPDU. If the destination (Dst) node receives an MPDU containing bit errors, the message shall not be acknowledged. An ACK request shall be used to indicate the need for ACK. + +###### 8.1.1.4.2.3 Retransmission + +If two or more nodes transmit MPDUs simultaneously, a collision may occur and the MPDUs may not reach their destinations. + +If the source (Src) node does not receive an ACK, it shall assume that the transmission was unsuccessful and in response it shall retry the MPDU transmission up to *aMacMaxFrameRetries* times. + +In order to avoid another collision, each TX shall delay a retransmission by a random delay. + +###### 8.1.1.4.2.4 Multi-hop routing + +The MAC layer defines MPDU header fields for support of multi-hop routing. Routing is outside the scope of this Recommendation. + +###### 8.1.1.4.2.5 Data validation + +An 8-bit non-correcting FCS mechanism is employed to detect bit errors for data rates R1 and R2. A 16-bit non-correcting FCS mechanism is employed to detect bit errors for data rate R3. Refer to clause 7.1.2.2 for details on data rates. + +##### 8.1.1.4.3 Power consumption considerations + +One category of battery-powered nodes spend most of their operational life in sleep mode. Such nodes may periodically wake up and poll other nodes to get pending messages. The PHY layer AL mode is used for listening during wake-up polling. + +Other low-power nodes may require a more responsive behaviour than can be achieved via periodic wake-up. Such nodes may use the PHY FL mode for incoming messages. + +###### 8.1.1.4.3.1 Communication with a frequently listening node (FLN) + +Battery-powered devices may need to be reachable at any time. Nodes that are listening at regular intervals are said to operate in FL mode. The PHY layer provides an extended preamble sequence that allows an FLN to operate at a very low duty cycle while still being reachable. + +### 8.1.2 MAC layer service specification + +The MAC layer provides an interface between higher layers, typically the network layer, and the PHY layer. The MLME provides the service interfaces through which MAC layer management functions may be invoked. The MLME is responsible for maintaining a database of managed objects pertaining to the MAC layer. This database is referred to as the MAC MIB. Figure 8-3 depicts the components and interfaces of the MAC layer. + + + +The diagram illustrates the MAC layer reference model. At the top, the 'Network layer' is shown. Below it, the 'MAC sublayer' is depicted, containing two Service Access Points (SAPs): 'MD-SAP' and 'PD-SAP'. To the right of the MAC sublayer, the 'MLME' (MAC Management Entity) is shown, which includes a 'MAC MIB' (Management Information Base). The MLME is connected to the MD-SAP and PD-SAP via 'MLME-SAP' and 'PLME-SAP' respectively. At the bottom, the 'PHY layer' is shown, connected to the MAC sublayer via the PD-SAP and PLME-SAP. The diagram is labeled 'G.9959(15)\_F8-3' at the bottom right. + +Figure 8-3 – MAC layer reference model diagram showing the Network layer, MAC sublayer, and PHY layer with their respective Service Access Points (SAPs) and Management Entity (MLME). + +Figure 8-3 – MAC layer reference model + +The MAC layer shall provide two services to the network layer, accessed through two SAPs: + +- The MD service, accessed through the MD-SAP; +- The MAC management service, accessed through the MLME-SAP. + +#### 8.1.2.1 MD service + +The MD-SAP supports the transport of a network layer protocol data unit (NPDU) (i.e., the MSDU) from the network layer to the PHY layer. Table 8-1 lists the primitives supported by the MD-SAP. + +**Table 8-1 – MD-SAP primitives** + +| MD-SAP Primitive | Request | Confirm | Indication | +|------------------|-----------|-----------|------------| +| MD-DATA | 8.1.2.1.1 | 8.1.2.1.2 | 8.1.2.1.3 | + +##### 8.1.2.1.1 MD-DATA.request + +The MD-DATA.request primitive requests the transfer of an NPDU (i.e., MSDU) from the network layer to the PHY entity. + +###### 8.1.2.1.1.1 Semantics of the service primitive + +The semantics of the MD-DATA. request primitive shall be as follows: + +``` +MD-DATA.request (SrcHomeID, + SrcNodeID, + DstNodeID, + msduLength, + msdu, + SequenceNumber, + TxType, + TxOptions, + BeamOption, + RateOption, + ChannelOption, + MulticastOption + ) +``` + +Table 8-2 specifies the parameters for the MD-DATA.request primitive. + +**Table 8-2 – MD-Data.request parameters** + +| Name | Type | Valid range | Description | +|----------------|------------|--------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| SrcHomeID | Byte Array | 0x00000000..0xFFFFFFFF | Domain identifier to use | +| SrcNodeID | Byte | 0x00..0xE8 | Source node identifier to use:
0x00: Uninitialized NodeID
0x01..0xE8: NodeID
0xE9..0xFE: Reserved | +| DstNodeID | Byte | 0x00..0xFF | Destination node identifier to use:
0x00: Reserved
0x01..0xE8: NodeID
0xE9..0xFE: Reserved
0xFF: Broadcast NodeID | +| msduLength | Byte | $\leq aMacMaxMSDU SizeX$ | Number of bytes to transmit | +| msdu | Byte Array | – | MSDU to transmit | +| SequenceNumber | Byte | – | Unique number of this frame
The same value shall be used for retransmissions | +| TxType | Byte | 0x01..0x03 | Transmission type to use:
0x01 = Singlecast or broadcast transmission | + +**Table 8-2 – MD-Data.request parameters** + +| Name | Type | Valid range | Description | +|-----------------|--------------------------|----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | 0x02 = Multicast transmission
0x03 = Acknowledged transmission | +| TxOptions | Byte | 0x01, 0x02, 0x04 | Transmission options for this MSDU
The control word is formed as a bitwise OR of one or more of the following values:
0x01 = Routed frame transmission
0x02 = Acknowledged transmission
0x04 = Low power transmission (Note 1) | +| BeamOption | Byte | 0x00, 0x02..0x04 | Battery support options
0x00: No beam
0x02: Short continuous beam
0x03: Long continuous beam
0x04: Fragmented beam | +| ChannelOption | Enumeration | Channel A,B, C (Note 2) | Channel to use | +| RateOption | Enumeration | Data Rate R1, R2, R3 according to the applied RF profile (see Tables 7-1, 7-2 and 7-3) | Data rate to use | +| MulticastOption | Byte + Bitmap (30 bytes) | – | If TxType is "Multicast transmission", this bitmap indicates the intended recipients | + +NOTE 1 – Bit 2 (0x04) controls which transmission power level the MAC layer requests from the PHY layer. +NOTE 2 – Channels A, B, and C are preconfigured to RF profiles from the list presented in clause 7.1.2.1 via MAC MIB attributes defined in Table 8-20. Channel configuration MAC MIB profiles map directly to PHY MIB profiles. + +###### 8.1.2.1.1.2 When generated + +The MD-DATA.request primitive is generated by the network layer and issued to the MAC entity to request the transfer of an NPDU (i.e., MSDU). + +The TxOptions.LowPower is an option targeting the PHY layer. The option shall make the MAC request the PHY power level defined by the MAC constant aMacTxPhyPowerLevelLow instead of aMacTxPhyPowerLevelNormal. + +###### 8.1.2.1.1.3 Effects on receipt + +The receipt of the MD-DATA.request primitive by the MAC entity shall cause the transmission of the supplied MSDU. + +The MAC entity builds an MPDU to transmit from the supplied parameters. The TxOptions parameters indicate optional parameters on how the MAC layer data service transmits the supplied MSDU. + +The MAC entity shall check for PHY CCA (see clause 8.1.5.1.1). If the PHY PLME-GET-CCA primitive returns TRUE, the MAC entity shall enable the TX by issuing the PLME-SET-TRX-MODE.request primitive with a mode of TX\_ON to the PHY. On receipt of the PLME-SET-TRX-MODE.confirm primitive with a status of either SUCCESS or TX\_ON, the constructed MPDU may then be transmitted by issuing the PD-DATA.request primitive. Finally, on receipt of the PD- + +DATA.confirm primitive, the MAC entity shall disable the TX by issuing the PLME-SET-TRX-MODE.request primitive to the PHY. + +If the TxOptions parameter specifies that acknowledged transmission is required, the MAC entity shall enable its receiver immediately following the transmission of the MPDU and wait for an ACK for at least *aMacMinAckWaitDuration* symbols. If the MAC entity does not receive an ACK within this time, it shall retransmit the MPDU one or more times as defined by *aMacMaxFrameRetries*. If the MAC entity still does not receive an ACK, it shall discard the MSDU and issue the MD-DATA.confirm primitive with a status of NO\_ACK. + +If the MPDU was successfully transmitted the MAC entity shall issue the MD-DATA.confirm primitive with a status of SUCCESS. + +If the MPDU could not be transmitted due to a busy channel (clause 8.1.5.1.1) the MAC entity shall issue the MD-DATA.confirm primitive with a status of NO\_CCA. + +If any parameter in the MD-DATA.request primitive is not supported or is out of range, the MAC entity shall issue the MD-DATA.confirm primitive with a status of INVALID\_PARAMETER. + +If the MSDU length is longer than *aMacMaxMSDUSizeX* the MAC entity shall issue the MD-DATA.confirm primitive with a status of FRAME\_TOO\_LONG. + +The MD-Data.request parameters are used to construct the MHR see clause 8.1.3. + +##### 8.1.2.1.2 MD-DATA.confirm + +The MD-DATA.confirm primitive confirms the transmission of an MSDU. + +###### 8.1.2.1.2.1 Semantics of the service primitive + +The semantics of the MD-DATA.confirm primitive shall be as follows: + +``` +MD-DATA.confirm ( + status +) +``` + +Table 8-3 specifies the parameters for the MD-DATA.confirm primitive. + +**Table 8-3 – MD-Data.confirm parameters** + +| Name | Type | Valid range | Description | +|--------|-------------|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| status | Enumeration | SUCCESS,
NO_ACK,
INVALID_PARAMETER,
NO_CCA,
FRAME_TOO_LONG | Transmission was successful
Transmission was not acknowledged
Transmission aborted; invalid parameter
Transmission aborted; no clear channel
Transmission aborted; frame too long | + +###### 8.1.2.1.2.2 When generated + +The MD-DATA.confirm primitive is generated by the MAC entity in response to an MD-DATA.request primitive. The MD-DATA.confirm primitive shall return a status as defined in Table 8-3. + +The primitive may be delayed if the MAC has to wait for an ACK. If the frame is transmitted using beaming (refer to clauses 8.1.3.11 and 8.1.3.13), the delay may be more than one second. + +###### 8.1.2.1.2.3 Effects on receipt + +The MD-DATA.confirm primitive allows higher layers to take proper action whether the transmission was successful or unsuccessful. + +##### 8.1.2.1.3 MD-DATA.indication + +The MD-DATA.indication primitive indicates the reception of an MSDU from the MAC entity to higher layer entities. + +###### 8.1.2.1.3.1 Semantics of the service primitive + +The semantics of the MD-DATA.indication primitive shall be as follows: + +``` +MD-DATA.indication ( + FrmType, + SrcHomeID, + SrcNodeID, + DstNodeID, + msduLength, + msdu, + SequenceNumber, + ChannelOption, + RateOption, + MulticastOption +) +``` + +Table 8-4 specifies the parameters for the MD-DATA.indication primitive. + +FrmType indicates if the data delivered to the network layer is a data frame or a beam fragment. Refer to clause 8.1.3.10 for details on beam fragments. + +**Table 8-4 – MD-DATA.indication parameters** + +| Name | Type | Valid range | Description | +|-------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FrmType | Enumeration | 0x01..0xFF | Code indicating the frame type:
0x00: Uninitialized type
0x01: Singlecast frame
0x02: Multicast frame
0x03: ACK frame
0x04..0x07: Not to be used (Note)
0x08: Routed frame
0x09: Beam fragment
0x0A..0xFF: Reserved | +| SrcHomeID | Byte Array | 0x00000000..
0xFFFFFFFF
The value 0x00000000 is reserved for un-initialized legacy nodes. HomeID 0x00000000 shall not be used for any domain. | The 4-byte domain identifier of the node from which the MSDU was received | +| SrcNodeID | Byte | 0x00..0xFF
The value 0x00 is reserved for un-initialized nodes. | NodeID of the originating node
0x00: Uninitialized NodeID
0x01..0xE8: NodeID
0xE9..0xFF: Reserved | +| DstNodeID
(Not applicable) | Byte | 0x00..0xFF | NodeID of the destination node
0x00: Reserved | + +**Table 8-4 – MD-DATA.indication parameters** + +| Name | Type | Valid range | Description | +|---------------------------|-----------------------------|-------------------------|--------------------------------------------------------------------------------------| +| for multicast frame type) | | | 0x01..0xE8: NodeID
0xE9..0xFE: Reserved
0xFF: Broadcast NodeID | +| msduChannel | Enumeration | Channel A, B, C | The channel from which the MSDU was received | +| msduRate | Enumeration | Data rate R1, R2, R3 | The bit rate of the received MSDU | +| msduLength | Byte | $\leq aMacMaxMSDUSizeX$ | The number of received bytes | +| msdu | Byte Array | – | The received MSDU | +| SequenceNumber | Byte | – | The unique number of this frame.
Use same value for retransmissions | +| MulticastOption | Byte + Bitmap
(30 bytes) | – | If TxType is "Multicast transmission", this bitmap indicates the intended recipients | + +NOTE – These values shall not be used due to backwards compatibility. + +In case of a beam frame, the SrcHomeID field shall be formatted as specified in clause 8.1.3.10. + +###### **8.1.2.1.3.2 When generated** + +The MD-DATA.indication primitive is generated by the MAC entity on receipt of a frame from the PHY layer. If the frame checksum is valid, the frame shall be forwarded to the network layer. + +###### **8.1.2.1.3.3 Effects on receipt** + +The network layer is notified of the arrival of data. + +Beam fragments shall also be forwarded to the network layer, which may then forward the beam fragment to higher layers. Higher layers of a node in FL mode may decide to re-enable sleep mode if the NodeID of a beam fragment is intended for another node. + +##### **8.1.2.1.4 Data service message sequence charts** + +Figure 8-4 illustrates the sequence of messages necessary for a successful data transfer between two nodes. + + + +``` + +sequenceDiagram + participant SNL as Source network layer + participant SML as Source MAC layer + participant DML as Destination MAC layer + participant DNL as Destination network layer + Note right of DNL: G.9959(15)_F8-4 + SNL->>SML: MD-DATA.request + SML->>DML: Data frame + DML-->>SML: ACK frame (Optional) + SML-->>SNL: MD-DATA.confirm + DML->>DNL: MD-DATA.indication + +``` + +Sequence chart showing MD service messages between Source network layer, Source MAC layer, Destination MAC layer, and Destination network layer. The sequence includes MD-DATA.request, Data frame, ACK frame (Optional), MD-DATA.confirm, and MD-DATA.indication. + +**Figure 8-4 – MD service message sequence chart** + +#### 8.1.2.2 MAC management service + +The MLME-SAP allows the transport of management commands between the next higher layer and the MLME. Table 8-5 summarizes the primitives supported by the MLME through the MLME-SAP interface. + +The primitives are discussed in the clauses referenced in the table. + +**Table 8-5 – MLME-SAP primitives** + +| MLME-SAP Primitive | Request | Confirm | Indication | Response | +|--------------------|-----------|-----------|------------|----------| +| MLME-GET | 8.1.2.2.1 | 8.1.2.2.2 | – | – | +| MLME-SET | 8.1.2.2.3 | 8.1.2.2.4 | – | – | +| MLME-RESET | 8.1.2.2.5 | 8.1.2.2.6 | – | – | + +##### 8.1.2.2.1 MLME-GET.request + +The MLME-GET.request primitive requests information about a given MAC MIB attribute. + +###### 8.1.2.2.1.1 Semantics of the service primitive + +The semantics of the MLME-GET.request primitive shall be as follows: + +MLME-GET.request ( + MacMibAttribute +) + +Table 8-6 specifies the parameters for the MLME-GET.request primitive. + +**Table 8-6 – MLME-GET.request parameters** + +| Name | Type | Valid range | Description | +|-----------------|---------|----------------|--------------------------------------------------| +| MacMibAttribute | Integer | See Table 8-20 | The identifier of the MAC MIB attribute to read. | + +###### 8.1.2.2.1.2 When generated + +The MLME-GET.request primitive is generated by the next higher layer and issued to the MLME to obtain information from the MAC MIB. + +###### 8.1.2.2.1.3 Effects on receipt + +On receipt of the MLME-GET.request primitive, the MLME shall retrieve the requested MAC MIB attribute from its database. If the identifier of the MAC MIB attribute is not found in the database, the MLME shall issue the MLME-GET.confirm primitive with a status of UNSUPPORTED\_ATTRIBUTE. + +If the requested MAC MIB attribute is successfully retrieved, the MLME shall issue the MLME-GET.confirm primitive with a status of SUCCESS and the MAC MIB attribute value. + +##### 8.1.2.2.2 MLME-GET.confirm + +The MLME-GET.confirm primitive reports the result of a MAC MIB attribute request. + +###### 8.1.2.2.2.1 Semantics of the service primitive + +The semantics of the MLME-GET.confirm primitive shall be as follows: + +MLME-GET.confirm ( + status, + +``` + +MacMibAttribute, +MacMibAttributeValue +) + +``` + +Table 8-7 specifies the parameters for the MLME-GET.confirm primitive. + +**Table 8-7 – MLME-GET.confirm parameters** + +| Name | Type | Valid range | Description | +|----------------------|-------------|------------------------------------|-------------------------------------------------------------| +| status | Enumeration | SUCCESS or UNSUPPORTED_ATTRIBUTE | The result of the request for MAC MIB attribute information | +| MacMibAttribute | Integer | See Table 8-20 | The identifier of the MAC MIB attribute that was read | +| MacMibAttributeValue | Various | Attribute specific, see Table 8-20 | The value of the indicated MAC MIB attribute that was read | + +###### **8.1.2.2.2.2 When generated** + +The MLME-GET.confirm primitive is generated by the MLME and issued to the next higher layer in response to an MLME-GET.request primitive. This primitive returns a status of either SUCCESS, indicating that the request to read a MAC MIB attribute was successful, or an error code of UNSUPPORTED\_ATTRIBUTE. + +###### **8.1.2.2.2.3 Effects on receipt** + +The MLME-GET.confirm primitive reports the result of the MAC MIB attribute request. If the request was successful, the requester may use the returned MIB attribute value. + +##### **8.1.2.2.3 MLME-SET.request primitives** + +The MLME-SET.request primitive may be used to request that the specified MAC MIB attribute is set to the specified value. + +###### **8.1.2.2.3.1 Semantics of the service primitive** + +The semantics of the MLME-SET.request primitive shall be as follows: + +``` + +MLME-SET.request ( + MacMibAttribute, + MacMibAttributeValue +) + +``` + +Table 8-8 specifies the parameters for the MLME-SET.request primitive. + +**Table 8-8 – MLME-SET.request parameters** + +| Name | Type | Valid range | Description | +|----------------------|---------|------------------------------------|--------------------------------------------------------| +| MacMibAttribute | Integer | See Table 8-20 | The identifier of the MAC MIB attribute to write. | +| MacMibAttributeValue | Various | Attribute specific, see Table 8-20 | The value to write to the indicated MAC MIB attribute. | + +###### 8.1.2.2.3.2 When generated + +The MLME-SET.request primitive is generated by the next higher layer and issued to the MLME to set the specified MAC MIB attribute. + +###### 8.1.2.2.3.3 Effects on receipt + +On receipt of the MLME-SET.request primitive, the MLME should set the specified MAC MIB attribute to the specified value. + +If a non-existent MAC MIB attribute is specified, the MLME shall not change any MIB attribute. + +If the specified value is invalid for the specified MAC MIB attribute, the MLME shall not change the MAC MIB attribute value. + +If the specified MAC MIB attribute is changed, the change should take effect immediately. + +##### 8.1.2.2.4 MLME-SET.confirm + +The MLME-SET.confirm primitive shall report the result of the requested MAC MIB attribute change. + +###### 8.1.2.2.4.1 Semantics of the service primitive + +The semantics of the MLME-SET.confirm primitive shall be as follows: + +``` +MLME-SET.confirm ( + status, + MacMibAttribute +) +``` + +Table 8-9 specifies the parameters for the MLME-SET.confirm primitive. + +**Table 8-9 – MLME-SET.confirm parameters** + +| Name | Type | Valid range | Description | +|-----------------|-------------|--------------------------------------------------------|--------------------------------------------------------------------------------------------| +| status | Enumeration | SUCCESS,
UNSUPPORTED_ATTRIBUTE
INVALID_PARAMETER | Attribute successfully changed
Attribute is not supported
Attribute value is invalid | +| MacMibAttribute | Integer | Table 8-20 | The identifier of the MAC MIB attribute that was written. | + +###### 8.1.2.2.4.2 When generated + +The MLME-SET.confirm primitive shall be generated by the MLME and issued to the next higher layer in response to an MLME-SET.request primitive. + +If a non-existent MAC MIB attribute is specified, the MLME shall advertise a status of UNSUPPORTED\_ATTRIBUTE. + +If the specified value is invalid for the specified MAC MIB attribute, the MLME shall advertise a status of INVALID\_PARAMETER. + +If the specified MAC MIB attribute is updated, the MLME shall advertise a status of SUCCESS. + +###### 8.1.2.2.4.3 Effects on receipt + +The next higher layer is notified of the result of the MAC MIB attribute change request. The next higher layer should verify that the status parameter advertises the status value SUCCESS. Refer to Table 8-9. + +##### 8.1.2.2.5 MLME-RESET.request + +The MLME-RESET.request primitive allows the next higher layer to request that the MLME performs a reset operation. + +###### 8.1.2.2.5.1 Semantics of the service primitive + +The semantics of the MLME-RESET.request primitive shall be as follows: + +MLME-RESET.request ( + SetDefaultMIB +) + +Table 8-10 specifies the parameter for the MLME-RESET.request primitive. + +**Table 8-10 – MLME-RESET.request parameters** + +| Name | Type | Valid range | Description | +|---------------|---------|---------------|--------------------------------------------------------------------------------| +| SetDefaultMIB | Boolean | TRUE
FALSE | Reset MAC entity and all MIB attributes
Reset MAC entity state machine only | + +###### 8.1.2.2.5.2 When generated + +The MLME-RESET.request primitive is generated by the next higher layer and issued to the MLME to request a reset of the MAC entity to its initial conditions. The MLME-RESET.request primitive is issued when a node is excluded from a domain. + +###### 8.1.2.2.5.3 Effects on receipt + +On receipt of the MLME-RESET.request primitive, the MLME shall issue the PLME-SET-TRX-STATE.request primitive with a state of TRX\_OFF. On receipt of the PLME-SET-TRX-STATE.confirm primitive, the MAC entity shall then be set to its initial conditions, clearing all internal variables to their default values. If the SetDefaultMIB parameter is set to TRUE, the MAC MIB attributes are set to their default values. + +If the PLME-SET-TRX-STATE.confirm primitive is successful, the MLME shall issue the MLME-RESET.confirm primitive with the status of SUCCESS. Otherwise, the MLME shall issue the MLME-RESET.confirm primitive with the status of DISABLE\_TRX\_FAILURE. + +##### 8.1.2.2.6 MLME-RESET.confirm + +The MLME-RESET.confirm primitive reports the results of the reset operation. + +###### 8.1.2.2.6.1 Semantics of the service primitive + +The semantics of the MLME-RESET.confirm primitive shall be as follows: + +MLME-RESET.confirm ( + status +) + +Table 8-11 specifies the parameter for the MLME-RESET.confirm primitive. + +**Table 8-11 – MLME-RESET.confirm parameters** + +| Name | Type | Valid range | Description | +|--------|-------------|--------------------------------|-----------------------------------------------------------------| +| status | Enumeration | SUCCESS
DISABLE_TRX_FAILURE | MAC entity successfully reset
Transceiver could not be reset | + +###### 8.1.2.2.6.2 When generated + +The MLME-RESET.confirm primitive is generated by the MLME and issued to the next higher layer in response to an MLME-RESET.request primitive and following the receipt of the PLME-SET-TRX-STATE.confirm primitive. + +###### 8.1.2.2.6.3 Effects on receipt + +On receipt of the MLME-RESET.confirm primitive, the next higher layer is notified of the request to reset the MAC entity. This primitive shall return a status as defined in Table 8-11. + +#### 8.1.2.3 MAC enumeration description + +This clause explains the meaning of the enumerations used in the primitives defined in the MAC layer specification. Table 8-12 shows a description of the MAC enumeration values. + +**Table 8-12 – MAC enumerations description** + +| Enumeration | Description | +|-----------------------|-----------------------------------------------------------------------------------------------| +| SUCCESS | The requested operation was completed successfully | +| DISABLE_TRX_FAILURE | The attempt to disable the transceiver has failed | +| FALSE | Control flag value for disabling a property | +| FRAME_TOO_LONG | The frame has a length that is greater than aMacMaxMSDUSizeX | +| INVALID_PARAMETER | A parameter in the primitive is out of the valid range | +| NO_ACK | No acknowledgement was received after aMacMaxFrameRetries | +| NO_CCA | No clear channel access was possible after a period of macCCARetryDuration | +| TRUE | Control flag value for enabling a property | +| UNSUPPORTED_ATTRIBUTE | A SET/GET request was issued with the identifier of a MAC MIB attribute that is not supported | + +### 8.1.3 MPDU format + +This clause specifies the format of the MPDU. Each MPDU consists of the following basic components: + +1. A MHR, which comprises addresses, frame control and length information; +2. A MD payload, of variable length, which contains information specific to the frame type; +3. An MFR, which contains a FCS. + +The MPDU is defined as a sequence of fields. All MPDU formats in this clause are depicted in the order in which they are transmitted by the PHY, from left to right, where the leftmost bit is transmitted first in time. Bits within each field are numbered from $k - 1$ (leftmost and most significant) down to 0 (rightmost and least significant), where the length of the field is $k$ bits. Bytes within each multi-byte field are numbered from 1 (leftmost and most significant) up to $n - 1$ (rightmost and least significant), where the length of the field is $n$ bytes. Bits within each byte are numbered from 7 (leftmost and most significant) down to 0 (rightmost and least significant). + +The general MPDU format comprises the fields MHR, Data payload and MFR. The general MPDU shall be formatted as illustrated in Figure 8-5. + +The MPDU formats for channel configurations 1, 2, and channel configuration 3 are explained in the following. + +Singlecast MPDUs shall use the formats outlined in Figures 8-5 and 8-6. + + + +| | | | | | | | | +|-----------|--------|----------------|---------------|--------|---------------------|--------------|--------| +| Bytes: | 4 | 1 | 2 | 1 | n | m | 1 or 2 | +| MAC layer | HomeID | Source node ID | Frame control | Length | Destination node ID | Data payload | FCS | +| | MHR | | | | MSDU | | MFR | +| | MPDU | | | | | | | + +G.9959(15)\_F8-5 + +Figure 8-5: General MPDU format (Channel configurations 1, 2). The diagram shows a table with 7 columns representing bytes: HomeID (4), Source node ID (1), Frame control (2), Length (1), Destination node ID (n), Data payload (m), and FCS (1 or 2). Below the table, labels indicate the MAC layer, MHR (MAC Header), MPDU (MAC Protocol Data Unit), MSDU (MAC Service Data Unit), and MFR (MAC Footer). + +**Figure 8-5 – General MPDU format (Channel configurations 1, 2)** + + + +| | | | | | | | | | +|-----------|--------|----------------|---------------|--------|-----------------|---------------------|--------------|-----| +| Bytes: | 4 | 1 | 2 | 1 | 1 | n | m | 2 | +| MAC layer | HomeID | Source node ID | Frame control | Length | Sequence number | Destination node ID | Data payload | FCS | +| | MHR | | | | | MSDU | | MFR | +| | MPDU | | | | | | | | + +G.9959(15)\_F8-6 + +Figure 8-6: General MPDU format (Channel configuration 3). This diagram is similar to Figure 8-5 but includes an additional 'Sequence number' field (1 byte) between 'Length' and 'Destination node ID'. The FCS field is 2 bytes. The labels MHR, MPDU, MSDU, and MFR are also present. + +**Figure 8-6 – General MPDU format (Channel configuration 3)** + +The multicast MPDU shall use the formats outlined in Figures 8-7 and 8-8. + + + +| | | | | | | | | | +|-----------|--------|----------------|---------------|--------|-------------------|--------------------|--------------|--------| +| Bytes: | 4 | 1 | 2 | 1 | 1 | 29 | m | 1 or 2 | +| MAC layer | HomeID | Source node ID | Frame control | Length | Multicast control | Multicast bit mask | Data payload | FCS | +| | MHR | | | | | MSDU | | MFR | +| | MPDU | | | | | | | | + +G.9959(15)\_F8-7 + +Figure 8-7: Multicast MPDU format (Channel configurations 1, 2). This diagram shows a multicast MPDU structure. It includes 'HomeID' (4), 'Source node ID' (1), 'Frame control' (2), 'Length' (1), 'Multicast control' (1), 'Multicast bit mask' (29), 'Data payload' (m), and 'FCS' (1 or 2). Labels for MAC layer, MHR, MPDU, MSDU, and MFR are included. + +**Figure 8-7 – Multicast MPDU format (Channel configurations 1, 2)** + + + +| | | | | | | | | | | +|-----------|--------|----------------|---------------|--------|-----------------|-------------------|--------------------|--------------|-----| +| Bytes: | 4 | 1 | 2 | 1 | 1 | 1 | 29 | m | 2 | +| MAC layer | HomeID | Source node ID | Frame control | Length | Sequence number | Multicast control | Multicast bit mask | Data payload | FCS | +| | MHR | | | | | | MSDU | | MFR | +| | MPDU | | | | | | | | | + +G.9959(15)\_F8-8 + +Figure 8-8: Multicast MPDU format (Channel configuration 3). This diagram is similar to Figure 8-7 but includes a 'Sequence number' (1 byte) between 'Length' and 'Multicast control'. The FCS field is 2 bytes. Labels for MAC layer, MHR, MPDU, MSDU, and MFR are included. + +**Figure 8-8 – Multicast MPDU format (Channel configuration 3)** + +Refer to clause 8.1.3.6.1 for details on transmission and processing of multicast MPDUs. + +#### **8.1.3.1 HomeID** + +The HomeID identifier field is 4 bytes in length and specifies the unique domain identifier. All nodes in a domain shall have the same HomeID. + + + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|----------------|---|---|---|---|---|---|---| +| 0 | HomeID (0) MSB | | | | | | | | +| 1 | HomeID (1) | | | | | | | | +| 2 | HomeID (2) | | | | | | | | +| 3 | HomeID (3) LSB | | | | | | | | + +G.9959(15)\_F8-9 + +Figure 8-9: Format of a HomeID field. This is a bit-level diagram showing a 4-byte HomeID field. The columns represent bits 7 through 0. The rows represent bytes 0 through 3. Byte 0 is the MSB (Most Significant Byte) and Byte 3 is the LSB (Least Significant Byte). + +**Figure 8-9 – Format of a HomeID field** + +The MAC layer shall support configuration of a promiscuous mode in which all MPDUs are forwarded to higher layers. Refer to clause 8.1.5.1.3. + +#### 8.1.3.2 Source NodeID + +The source NodeID is 8 bits in length and shall be a unique identifier of a node in a given domain. Together with the HomeID, the source NodeID identifies the node that originated the MPDU. + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|---------------|---|---|---|---|---|---|---| +| 4 | Source NodeID | | | | | | | | + +G.9959(15)\_F8-10 + +**Figure 8-10 – Source NodeID field** + +The source NodeID shall comply with Table 8-13. + +**Table 8-13 –Source NodeID values** + +| NodeID value | Description | +|--------------|----------------------| +| 0x00 | Uninitialized NodeID | +| 0x01..0xE8 | NodeID | +| 0xE9..0xFF | Reserved | + +#### 8.1.3.3 Frame control + +The frame control field is 16 bits in length and contains information defining the frame type and other control flags. The frame control field shall be formatted as illustrated in Figures 8-11 and 8-12. + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|----------|---------------|-----------|----------------|-----------------|---|---|---| +| 5 | Routed | ACK Req. | Low power | Speed modified | Header type | | | | +| 6 | Reserved | Beaming Info. | | Reserved | Sequence number | | | | + +G.9959(15)\_F8-11 + +**Figure 8-11 –Frame control field (Channel configurations 1, 2)** + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|----------|---------------|----------|----------|-------------|---|---|---| +| 5 | ACK Req. | Low power | Reserved | | Header type | | | | +| 6 | Reserved | Beaming Info. | | Reserved | | | | | + +G.9959(15)\_F8-12 + +**Figure 8-12 – Frame Control field (Channel configuration 3)** + +##### 8.1.3.3.1 Routed subfield (Channel configurations 1, 2 only) + +The routed subfield is 1 bit in length. It shall be set to 0 when the MPDU is not routed and set to 1 when the MPDU is routed. The use of this field is out of scope of this Recommendation. + +##### 8.1.3.3.2 ACK Req subfield + +The ACK Req subfield is 1 bit in length. It shall be set to 1 when the source node wants the destination node to acknowledge the MPDU and set to 0 when no ACK is needed. + +A receiving node shall return an ACK MPDU in response to the ACK request. + +##### 8.1.3.3.3 Low power subfield + +The Low power subfield is 1 bit in length. It shall be set by the source node. The bit informs a destination node that the actual transmission was using low power. + +A receiving node shall return an ACK MPDU in low power in response to the low-power bit. + +##### 8.1.3.3.4 Speed modified subfield (Channel configurations 1, 2 only) + +The speed modified subfield is 1 bit in length. It shall be set to 1 if an MPDU is sent at a lower speed than supported by the Src and Dst. The field shall not be used for routed and multicast MPDUs. The field shall be set to 0 if the MPDU is sent at the highest speed supported by the source and destination. + +##### 8.1.3.3.5 Header type subfield + +The header type subfield defines the frame header type. + +**Table 8-14 – Header type** + +| Header type value | Description | +|-------------------|--------------------------------------------| +| 0x1 | Singlecast MPDU | +| 0x2 | Multicast MPDU | +| 0x3 | Acknowledgement MPDU | +| 0x4..0x7 | Not to be used (Note) | +| 0x8 | Routed MPDU (Channel configuration 3 only) | +| 0x9..0xB | Not to be used (Note) | +| 0xC..0xF | Reserved | + +NOTE – These values shall not be transmitted due to backward compatibility. Received frames shall be forwarded to higher layers. + +A broadcast MPDU is a singlecast MPDU (header type 0x1) carrying DstNodeID = 0xFF; see clause 8.1.3.6. + +A receiving node shall forward routed MPDUs to higher layers. The transmission of routed MPDUs is out of scope of this Recommendation. + +##### 8.1.3.3.6 Beaming information + +The beaming information sub-field shall advertise the capability of a sending FL node to be awakened by a beam if it is asleep. The beaming information sub-field shall be interpreted in combination with the actual channel configuration. + +**Table 8-14a – Beaming information, channel configurations 1, 2** + +| Channel configuration | Beam information value | Description | +|-----------------------|----------------------------|-----------------------| +| 1,2 | Frame Control[6..5] = "00" | No beam | +| 1,2 | Frame Control[6..5] = "01" | Short continuous beam | +| 1,2 | Frame Control[6..5] = "10" | Long continuous beam | +| 1,2 | Frame Control[6..5] = "11" | Reserved | + +**Table 8-14b – Beaming information, channel configuration 3** + +| Channel configuration | Beam information value | Description | +|-----------------------|-----------------------------|-----------------| +| 3 | Frame Control[6..4] = "000" | Reserved | +| 3 | Frame Control[6..4] = "001" | Reserved | +| 3 | Frame Control[6..4] = "010" | Reserved | +| 3 | Frame Control[6..4] = "011" | Reserved | +| 3 | Frame Control[6..4] = "100" | Fragmented beam | +| 3 | Frame Control[6..4] = "101" | Reserved | +| 3 | Frame Control[6..4] = "110" | Reserved | +| 3 | Frame Control[6..4] = "111" | Reserved | + +##### **8.1.3.3.7 Sequence Number (Channel configurations 1, 2 only)** + +The Sequence Number is a 4-bit sub-field of the Frame Control field. The Sequence Number is provided by higher layers when transmitting. The MAC layer of a transmitting node shall forward the Sequence Number value transparently to the PHY. The MAC layer of a receiving node shall forward the Sequence Number value transparently to higher layers. + +The MAC layer shall use the same sequence number for the initial transmission and for all retransmissions of a given MPDU. The transmitted sequence number shall be in the range 0x1..0xf. The value 0xf shall be followed by the value 0x1. + +A receiving node shall accept any sequence number value in the range 0x0..0xf. The receiving node shall return the same value in an ACK MPDU if ACK is requested. A transmitting node shall validate the received sequence number in an ACK MPDU. In order to support legacy implementations, a transmitting node which receives an ACK MPDU shall accept the sequence number value zero irrespective of the sequence number transmitted. + +#### **8.1.3.4 Length** + +The length field is 1 byte in length and shall indicate the length of the MPDU in bytes. + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|--------|---|---|---|---|---|---|---| +| 7 | Length | | | | | | | | + +G.9959(15)\_F8-13 + +**Figure 8-13 – Length field** + +The length is limited to *aMacMaxMSDUSizeX*. The actual values can be found in Table 8-18. A receiving node shall not accept more bytes than the maximum length allowed for the actual data rate. + +#### **8.1.3.5 Sequence number (Channel configuration 3 only)** + +The sequence number is an 8-bit field of the MPDU header (MHR). The MAC layer of a transmitting node shall forward the sequence number value transparently to the PHY. The MAC layer of a receiving node shall forward sequence number value transparently to higher layers. + +The MAC layer shall use the same sequence number for the initial transmission and for all retransmissions of a given MPDU. The transmitted sequence number shall be in the range 0x00..0xff. The value 0xff shall be followed by the value 0x00. + +A receiving node shall accept any sequence number value in the range 0x00..0xff. The receiving node shall return the same value in an ACK MPDU if ACK is requested. A transmitting node shall validate the received sequence number in an acknowledgement MPDU. + +#### 8.1.3.6 Destination NodeID + +The destination NodeID shall specify a destination node in the same domain identified by the HomeID. + +The destination NodeID value shall comply with Table 8-15. + +**Table 8-15 – Destination NodeID** + +| NodeID | Node type | +|------------|----------------------| +| 0x00 | Uninitialized NodeID | +| 0x01..0xE8 | NodeID | +| 0xE9..0xFE | Reserved | +| 0xFF | Broadcast NodeID | + +The DstNodeID value 0xFF may be used for broadcasting a MPDU to all nodes within direct range. The MAC layer of a receiving node shall always forward a broadcast MPDU to higher layers. + +The MAC layer shall support the configuration of a promiscuous receiver mode, forwarding all MPDUs to higher layers irrespective of the actual Dst NodeID. + +##### 8.1.3.6.1 Multicast destination fields + +A multicast MPDU shall carry a multicast control field and a multi-byte multicast bit mask as shown in Figure 8-14. + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|----------------|---|---|----------------------|---|---|---|---| +| 8 | Address Offset | | | Number of mask bytes | | | | | +| 9 | | | | Mask byte 0 | | | | | +| 10 | | | | Mask byte 1 | | | | | +| 11 | | | | Mask byte 2 | | | | | +| ... | | | | ..... | | | | | +| 37 | | | | Mask byte 28 | | | | | + +G.9959(15)\_F8-14 + +**Figure 8-14 – Multicast destination fields** + +A receiving node shall not acknowledge a multicast MPDU. A sending node shall set the ACK Req bit of a multicast MPDU to zero. Likewise, a sending node shall set the address offset field to zero and the number of mask bytes field shall be set to 29. + +A receiving node shall support the values of the Address Offset field outlined in Table 8-16. A receiving node shall support values of the number of Mask Bytes field in the range 1..29. + +The address offset field is a 3 bit field. The encoding of the field is outlined in Table 8-16. + +**Table 8-16 – Multicast address offset encoding** + +| Address offset value | Bit address offset | +|----------------------|--------------------| +| 0 | 0 | +| 1 | 32 | +| 2 | 64 | +| 3 | 96 | +| 4 | 128 | +| 5 | 160 | +| 6 | 192 | +| 7 | 224 | + +Each bit of a mask byte represents a NodeID. Mask byte 0 represents NodeIDs 1 to 8. + +As an example a mask byte 0 value of 0xC5 (in binary: 11000101) covers NodeIDs 1, 3, 7 and 8 while a mask byte 1 value of 0xC5 (in binary: 11000101) covers NodeIDs 9, 11, 15 and 16. + +The destination NodeID can be calculated using the following formula. + +$$\text{Dst NodeID} = \text{bit address offset} + \text{mask byte number} \times 8 + \text{mask bit number} + 1$$ + +#### 8.1.3.7 Data Payload + +The Data Payload field has a variable length. An ACK MPDU may carry zero or more data payload bytes. A receiving node may derive the length of the Data Payload field from the MPDU Length field. + +#### 8.1.3.8 FCS + +An 8-bit non-correcting FCS shall be used for validating the MPDU integrity for date rates R1 and R2. The FCS shall be calculated from the HomeID field to the Data Payload field, both included, as shown in Figure 8-15. + + + +The diagram shows an MPDU structure with the following fields: HomeID, Source node ID, Frame control, Length, Destination node ID, Data payload, and FCS. A bracket labeled 'FCS coverage' spans from the start of the HomeID field to the end of the Data payload field, indicating the data included in the FCS calculation. The source G.9959(15)\_F8-15 is noted at the bottom right. + +Diagram of MPDU structure showing fields: HomeID, Source node ID, Frame control, Length, Destination node ID, Data payload, and FCS. A bracket labeled 'FCS coverage' spans from the start of HomeID to the end of Data payload. + +**Figure 8-15 – FCS coverage** + + + +The diagram shows the FCS field structure, which is an 8-bit byte. The bits are numbered 7 down to 0. The label 'Frame check sequence' is placed across the bits. The source G.9959(15)\_F8-16 is noted at the bottom right. + +Diagram of the FCS field structure showing 8 bits (0-7) and the label 'Frame check sequence'. + +**Figure 8-16 – FCS field** + +The FCS shall be calculated as an odd (XOR'ed) checksum as shown in the following algorithm. + +``` + +BYTE GenerateCheckSum(BYTE *Data, BYTE Length) +{ + BYTE CheckSum = 0xFF; + for (; Length > 0; Length--) + { + CheckSum ^= *Data++; + } + return CheckSum; +} + +``` + +#### 8.1.3.9 Cyclic redundancy code (CRC) + +A 16-bit non-correcting CRC shall be used for validating the MPDU integrity for data rate R3. + + + +Diagram of MPDU structure showing CRC coverage. The MPDU consists of HomeID, Source node ID, Frame control, Length, Destination node ID, Data payload, and CRC. A double-headed arrow labeled 'CRC' spans from the start of the MPDU to the start of the CRC field. A dashed vertical line separates the Data payload from the CRC field. The text 'G.9959(15)\_F8-17' is at the bottom right. + +Figure 8-17 – CRC coverage + +The CRC-16 generator polynomial shall be: + +$$P(x) = x^{16} + x^{12} + x^5 + 1, \text{ also known as CRC-CCITT}$$ + +The CRC 16 shall be calculated over the whole MPDU, except for the preamble, SOF, and the CRC-16 fields. + +The CRC-16 generator shall be initialized to 1D0Fh before applying the first byte of a frame. Additional bits shall not be appended to the frame data. + +#### 8.1.3.10 Beam frame format + +Beam frames may be used to awaken battery powered nodes operating in FL mode. Beam frames are used for several beam types. Beam frames are transmitted back to back to ensure an FL node can detect a beam within a very short time window before returning to sleep. + +Each beam frame carries a preamble sequence and an SOF field, just like the start of any other PHY PDU. The SOF is followed by two or three bytes, replacing the HomeID field found in a general MPDU. A receiving node may distinguish a general MPDU from a beam frame by inspecting the MS byte of the HomeID. If this byte carries a beam tag (refer to Table 8-17) this is a beam frame and the following one or two bytes carry beaming relevant information. + + + +Diagram of Beam frame format. The frame consists of a Preamble sequence (8/20 bytes), Start of frame (1 byte), Beam Tag = 0x55 (1 byte), NodeID (1 byte), and an optional HomeID hash (1 byte). The first four bytes are labeled as the 'PPDU header'. The last byte is labeled as the '(Start of) MPDU header'. A dashed box around the HomeID hash is labeled '(Optional)'. A double-headed arrow labeled 'HomeID of general MPDU' spans from the start of the Beam Tag to the start of the HomeID hash. The text 'G.9959(15)\_F8-18' is at the bottom right. + +Figure 8-18 – Beam frame (Tag = 0x55) + +The preamble sequence length depends on the actual RF profile used. Refer to clauses 7.1.2.1 and 7.1.3.2. A node shall listen long enough to detect a beam frame during worst case conditions around the SOF, beam tag, and beam information. In a worst-case situation, a node in FL mode starts listening just when it is too late to achieve lock to the preamble sequence. In this case, the node has to wait until another preamble sequence starts. Only after achieving lock to the preamble, the SOF and beam tag fields may be correctly decoded. + +Each beam frame shall carry the Beam Tag and NodeID fields. The NodeID field should be followed by the optional HomeID Hash field. + +**Table 8-17 – Beam frame fields** + +| Field name | Value | Description | +|---------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Beam Tag | 0x55 | HomeID MSB reserved for beam frame transmission.
HomeIDs in the range 0x55000000..0x55FFFFFF shall not be assigned to any domain
The Beam Tag value 0x55 shall advertise the presence of a NodeID field and an optional HomeID Hash field | +| | 0x54
( reserved ) | HomeID MSB reserved for beam frame transmission
HomeIDs in the range 0x54000000..0x54FFFFFF shall not be assigned to any domain
The beam tag value 0x54 shall be reserved for future use | +| NodeID | 1..232, 255 | Destination NodeID. If the value is 255 or it matches the NodeID of an FL node, the node shall also inspect the HomeID Hash field. If no match is found, the FL node should return to sleep. | +| HomeID Hash
(optional) | Hashed 8-bit version of the HomeID.
Ignore if 0x0A, 0x4A or 0x55. | Hash value for preventing NodeID collisions in dense network environments with overlapping domains
Refer to the text following this table | + +It is recommended that support is implemented for the HomeID Hash field presented in Figure 8-18 and Table 8-17. + +The HomeID hash value shall be calculated as shown in the following algorithm. + +``` + +BYTE GenerateHomeIdHash (BYTE *HomeId) +{ + BYTE HomeIdHash = 0xFF; + for (Length = 4; Length > 0; Length--) + { + HomeIdHash ^= *HomeId++; + } + switch (HomeIdHash) + { + Case 0x0A: + Case 0x4A: + Case 0x55: + HomeIdHash++; + } + return HomeIdHash; +} + +``` + +A sending node should include a HomeID hash field in the beam frame (Tag 0x55) to assist FL nodes in filtering out beam frames belonging to other domains. + +A FL node receiving one of the HomeID hash values 0x0A, 0x4A or 0x55 shall accept the value as a potential match to the actual HomeID and therefore it shall stay awake to receive the MPDU that follows if there is a match for the NodeID. Likewise, a FL node shall stay awake to receive the MPDU that follows if it detects a match to the hashed version of its own HomeID and if there is also a match + +for the actual NodeID. In case of no match for HomeID hash and/or NodeID, the node may return to sleep immediately. + +#### 8.1.3.11 Fragmented beam format + +A beam fragment shall comprise a number of beam frames. The beam fragment duration shall be in the range 110-115 ms. Beam frames shall be sent back to back to ensure that the beam fragment can be detected by a node waking up at any moment during the duration of the beam fragment. + + + +Figure 8-19: Format of the beam fragment. The diagram shows a sequence of four 'Beam frame' blocks followed by an ellipsis and a 'Beam fragment' block. A horizontal dashed line spans the entire sequence, labeled '110 ms'. Below the sequence, a solid grey bar is labeled 'Beam fragment'. The text 'G.9959(15)\_F8-19' is in the bottom right corner. + +**Figure 8-19 – Format of the beam fragment** + +A fragmented beam shall comprise a number of beam fragments. The next beam fragment shall begin in the range 190-200 ms measured from the beginning of the previous beam fragment. Fragmented beams shall be sent at data rate R3. A receiver shall be able to monitor multiple channels for beam frames. + + + +Figure 8-20: Format of the fragmented beam. The diagram shows three 'Beam fragment' blocks separated by ellipses. Above the first fragment is a duration of '110.. 115 ms'. Above the second fragment is a duration of '110.. 115 ms'. Above the third fragment is a duration of '110.. 115 ms'. Below the first fragment is a duration of '190.. 200 ms'. A horizontal dashed line spans the entire sequence, labeled '3000 ms'. Below the sequence, a solid grey bar is labeled 'Fragmented beam'. The text 'G.9959(15)\_F8-20' is in the bottom right corner. + +**Figure 8-20 – Format of the fragmented beam** + +Proper TX scheduling allows a sending node to reach sleeping nodes that use a range of wakeup intervals 100 ms, 150 ms, 250 ms, 500 ms, 700 ms, 900 ms. The chosen wakeup interval should be a trade-off between battery lifetime and response time. + +A fragmented beam may address any NodeID and also the broadcast NodeID 0xFF. A full fragmented beam shall span 3 000 ms. A singlecast frame shall follow the fragmented beam. A receiving node may interrupt the transmission of a fragmented beam by acknowledging a singlecast beam fragment. A receiving node shall not acknowledge a broadcast beam fragment. A receiving FL node detecting a positive match for the HomeID Hash field of the beam frame may return the ACK MPDU immediately. A receiving FL node not detecting a positive match for the HomeID hash field shall apply a random delay of 0..50 ms to the ACK MPDU to prevent collisions between FL nodes having the same NodeID in different domains. + +In response to an ACK MPDU, the originating node shall transmit the MPDU to the receiving node if the source HomeID of the ACK MPDU matches the HomeID of the beaming node. If the HomeID or NodeID does not match, the originating node shall ignore the ACK MPDU. + +#### 8.1.3.12 Continuous beam format + +A continuous beam is a series of beam frames spanning a fixed period of time. The beam frames shall be sent back to back to prevent other TXs from interrupting the continuous beam. The continuous beam shall be sent at data rate R2. + +A continuous beam may address any NodeID and also the broadcast NodeID (0xFF). + +There are two types of continuous beams: long and short. A long continuous beam may last for a maximum of 1 160 ms, and a short one may last for a maximum of 300 ms. The recommended duration is 1 100 ms for a long continuous beam and 275 ms for a short continuous beam. A continuous beam shall always be followed by a singlecast frame. + +#### 8.1.3.13 Beam formats on channel configurations 1 and 2 + +FL nodes operating in channel configuration 1 or 2 shall be able to receive and transmit the continuous beam format at data rate R2. + +#### 8.1.3.14 Beam formats on channel configuration 3 + +FL nodes operating in channel configuration 3 shall be able to receive and transmit the fragmented beam format at data rate 3. + +### 8.1.4 MAC constants and MIB attributes + +This clause specifies the constants and attributes used by the MAC. + +#### 8.1.4.1 MAC constants + +The constants used by the MAC layer are presented in Table 8-18. These constants are hardware dependent and cannot be changed during operation. + +**Table 8-18 – MAC constants in general** + +| Constants | Description | Value | +|----------------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------------| +| aMacMaxMSDUSizeR1 | The maximum singlecast/broadcast MSDU size for data rate R1 | 54 bytes | +| aMacMaxMSDUSizeMultiR1 | The maximum multicast MSDU size for data rate R1 | 25 bytes | +| aMacMaxMSDUSizeR2 | The maximum singlecast/broadcast MSDU size for data rate R2 | 54 bytes | +| aMacMaxMSDUSizeMultiR2 | The maximum multicast MSDU size for data rate R2 | 25 bytes | +| aMacMaxMSDUSizeR3 | The maximum singlecast/broadcast MSDU size for data rate R3 | 158 bytes | +| aMacMaxMSDUSizeMultiR3 | The maximum multicast MSDU size for data rate R3 | 129 bytes | +| aMacMinAckWaitDuration | The minimum ACK wait duration | $aPhyTurnaroundTimeRxTx + (aMacTransferAckTimeTX * (1/\text{data rate}))$ | +| aMacMaxFrameRetries | The number of retries after a transmission failure | 2 | +| aMacMinCCARetryDuration | The minimum duration of clear channel access assessment | 1100 ms | +| aMacTxPhyPowerLevelLow | The value used for phyTransmitPower to transmit at low power | Implementation dependent | +| aMacTxPhyPowerLevelNormal | The value used for phyTransmitPower to transmit at normal power | Implementation dependent | + +The term *aMacMaxMSDUSizeX* is used in text that applies to all data rates (*aMacMaxMSDUSizeR1*, *aMacMaxMSDUSizeR2*, *aMacMaxMSDUSizeR3*, *aMacMaxMSDUSizeMultiR1*, *aMacMaxMSDUSizeMultiR2*, *aMacMaxMSDUSizeMultiR3*). + +Table 8-19 outlines the constant values to use for message transfer at data rates R1, R2, R3. + +**Table 8-19 – MAC constants for MPDU transfer** + +| Constants | Description | R1 | R2 | R3 | | +|-------------------------------------|---------------------------------------------------------------------------|----------|----------|------------------|---------------| +| | | | | Channel Cfg 1, 2 | Channel Cfg 3 | +| aMacTransferAckTimeTX (ch) | The number of symbols of an ACK MPDU; including preamble | 168 bits | 248 bits | 416 bits | 296 bits | +| aMacTypicalFrameLengthTX(ch) | The number of symbols of a singlecast MPDU with a data payload of 4 bytes | 200 bits | 280 bits | 448 bits | 328 bits | +| aMacMinRetransmitDelay | Random backoff shall be higher than this value | 10 ms | | | | +| aMacMaxRetransmitDelay | Random backoff shall be lower than this value | 40 ms | | | | + +The MAC determines if the PHY is configured for channel configurations 1, 2 or channel configuration 3 operation by evaluating the RF profile mappings configured via the *macMapPhyChannel\** MAC MIB parameters and the RF profile table defined for the PHY. + +#### 8.1.4.2 MAC MIB attributes + +The MAC MIB comprises the attributes required to manage the MAC layer. Each of these attributes can be read or written using the MLME-GET.request and MLME-SET.request primitives respectively. The attributes contained in the MAC MIB are presented in Table 8-20. + +**Table 8-20 – MAC MIB attributes** + +| Attribute | Type | Range | Description | Default | +|----------------------------|------------|-------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------| +| macCCARetryDuration | Integer | aMacMinCCARetryDuration – infinite | The duration of clear channel access assessment | ~ 1100 ms | +| macHomeID | Byte array | 0x00000000..0xFFFFFFFF | The HomeID is the unique domain identifier | (random) | +| macNodeID | Byte | 0x00..0xFF | The NodeID is the address of the individual nodes in a domain | 0x00 | +| macPromiscuousMode | Boolean | TRUE or FALSE | This indicates whether the MAC layer is in a promiscuous (receive all) mode. A value of TRUE indicates that the | FALSE | + +**Table 8-20 – MAC MIB attributes** + +| Attribute | Type | Range | Description | Default | +|--------------------------|---------|-------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------| +| | | | MAC layer accepts all frames received from the PHY | | +| macRxOnWhenIdle | Boolean | TRUE or FALSE | This indicates whether the MAC layer is to enable its receiver at any time | FALSE | +| macMapPhyChannelA | Integer | Available RF profiles (Refer to clause 7.1.2.1) | Apply RF profile to channel A. Parameter maps directly to the PHY MIB parameter phyMapChannelA . | – | +| macMapPhyChannelB | Integer | Available RF profiles (Refer to clause 7.1.2.1) | Apply RF profile to channel B. Parameter maps directly to the PHY MIB parameter phyMapChannelB . | – | +| macMapPhyChannelC | Integer | Available RF profiles (Refer to clause 7.1.2.1) | Apply RF profile to channel C. Parameter maps directly to the PHY MIB parameter phyMapChannelC . | – | + +### 8.1.5 MAC functional description + +This clause provides a detailed description of the MAC functionality. Throughout this clause, the receipt of an MPDU is defined as the successful receipt of an incoming MPDU from the RF media to the PHY and the successful verification of the FCS by the MAC layer, as described in clause 8.1.3.8. + +#### 8.1.5.1 Transmission, reception and acknowledgement + +This clause describes the fundamental procedures for transmission, reception and acknowledgement. + +##### 8.1.5.1.1 Clear channel access + +The MAC layer shall request the channel status from the PHY layer. + +A PLME-GET-CCA.request message is used to evaluate the channel. A PLME-GET-CCA.confirm message returns the current channel status. + +If the MAC layer finds the channel busy for a period of *macCCARetryDuration* the transmission has failed. This shall be indicated to the network layer via the MD-DATA.confirm primitive with a status of NO\_CCA (see clause 8.1.2.1.2). + +##### 8.1.5.1.2 Transmission + +To avoid RF collisions, the MAC layer shall perform a CCA before transmitting. If the channel is found idle, the MPDU may be transmitted. The sourceHomeID and source NodeID field shall identify the sending node and the destination NodeID field shall identify the destination node. + +##### 8.1.5.1.3 Reception and rejection + +Each node may choose whether the MAC layer is to enable its receiver during idle periods. During these idle periods, the MAC layer shall still service TRX task requests from the network layer. A TRX task shall be defined as a transmission request, a reception request, or a clear channel access detection. On completion of each TRX task, the MAC layer shall request that the PHY enables or disables its receiver, depending on whether *macRxOnWhenIdle* is set to TRUE or FALSE, respectively. + +Due to the broadcast nature of radiocommunications, a node is able to receive and decode transmissions from all nodes that are operating on the same channel(s). The MAC layer shall be able to filter incoming frames and present only the frames that are of interest to the upper layers. + +In promiscuous mode, the MAC layer shall pass all MPDUs directly to the network layer. If the MAC layer is not in promiscuous mode (i.e., *macPromiscuousMode* is set to FALSE), it shall only accept MPDUs and issue an MD-DATA.indication to the network layer if the MPDU header contains the HomeID and NodeID of the receiving node. MPDUs shall also be accepted if addressed to the broadcast address or if the NodeID is included in a multicast header. + +If the frame type subfield indicates a singlecast MPDU and the ACK request subfield of the frame control field is set to 1, the MAC layer shall send an ACK MPDU. + +The MAC layer shall be able to receive beam fragments and forward these to higher layers. + +###### 8.1.5.1.3.1 RX filtering + +An MPDU shall be discarded if the received MPDU has an invalid FCS value. + +An MPDU shall be discarded if it has a length field less than 9 or greater than the maximum size values indicated in Table 8-18. + +##### 8.1.5.1.4 Use of ACK + +A singlecast MPDU may be sent with the ACK request subfield of the frame control field set to 1. Any multicast or broadcast MPDU shall be sent with the ACK request subfield set to 0. + +Sequence number checking shall be done as part of the ACK handling. Refer to clause 8.1.3.3.7. + +###### 8.1.5.1.4.1 No ACK + +An MPDU transmitted with its ACK request subfield set to 0 shall not be acknowledged by its intended recipient. The originating node shall assume that the transmission was successful. The sequence diagram in Figure 8-21 shows the scenario for transmitting a single MPDU without requiring an ACK. + + + +The diagram illustrates the interaction between four entities: Source network layer, Source MAC layer, Destination MAC layer, and Destination network layer. The sequence of messages is as follows: 1. The Source network layer sends an MD-DATA.request (ACK = 0) to the Source MAC layer. 2. The Source MAC layer sends a Data frame to the Destination MAC layer. 3. The Source MAC layer receives an MD-DATA.confirm from the Source network layer. 4. The Destination MAC layer sends an MD-DATA.indication to the Destination network layer. No ACK is sent from the Destination MAC layer back to the Source MAC layer. + +``` +sequenceDiagram + participant SNL as Source network layer + participant SML as Source MAC layer + participant DML as Destination MAC layer + participant DNL as Destination network layer + Note right of DNL: G.9959(15)_F8-21 + SNL->>SML: MD-DATA.request (ACK = 0) + SML-->>SNL: MD-DATA.confirm + SML->>DML: Data frame + DML->>DNL: MD-DATA.indication +``` + +Sequence diagram for successful transmission without acknowledgement + +Figure 8-21 – Successful transmission without acknowledgement + +###### 8.1.5.1.4.2 ACK + +A singlecast MPDU transmitted with the ACK request subfield of its frame control field set to 1 shall be acknowledged by the recipient. If the intended recipient correctly receives the MPDU, it shall + +return an ACK MPDU. Only the singlecast MPDU may be sent with the ACK request subfield set to 1. For other MPDU types the ACK request subfield shall be ignored by the intended recipient. + +The transmission of an ACK MPDU shall not commence before *aPhyTurnaroundTimeRXTX* symbols have elapsed after the reception of the last symbol of the frame. Refer to clause 7.1.2.5.9. + +The sequence diagram in Figure 8-22 shows the transmission of a singlecast MPDU with an ACK MPDU. + + + +``` +sequenceDiagram + participant SNL as Source network layer + participant SML as Source MAC layer + participant DML as Destination MAC layer + participant DNL as Destination network layer + Note right of DNL: G.9959(15)_F8-22 + SNL->>SML: MD-DATA.request (ACK = 1) + SML->>DML: Data frame (ACK = 1) + DML->>SML: ACK + SML->>SNL: MD-DATA.confirm + DML->>DNL: MD-DATA.indication +``` + +Sequence diagram showing successful transmission with ACK. Lifelines: Source network layer, Source MAC layer, Destination MAC layer, Destination network layer. The Source network layer sends an MD-DATA.request (ACK = 1) to the Source MAC layer. The Source MAC layer sends a Data frame (ACK = 1) to the Destination MAC layer. The Destination MAC layer sends an ACK back to the Source MAC layer. The Source MAC layer sends an MD-DATA.confirm to the Source network layer. The Destination MAC layer sends an MD-DATA.indication to the Destination network layer. + +**Figure 8-22 – Successful transmission with ACK** + +###### 8.1.5.1.4.3 Retransmission + +A node that sends a singlecast MPDU with its ACK request subfield set to 1 shall wait for a minimum of *aMacMinAckWaitDuration* symbols for the corresponding ACK MPDU to be received. If an ACK MPDU is received within *aMacMinAckWaitDuration* symbols and contains the correct HomeID and source NodeID, the transmission is considered successful, and no further action shall be taken by the originator. If an ACK MPDU is not received within *aMacMinAckWaitDuration* symbols, the transmission attempt has failed. The originator shall repeat the process of transmitting the MPDU and waiting for the ACK MPDU up to *aMacMaxFrameRetries* times. Before retransmitting, the node shall wait for a random backoff period (see clause 8.1.5.1.4.4). + +If an ACK MPDU is still not received after *aMacMaxFrameRetries* retransmissions, the MAC layer shall assume the transmission has failed and notify the network layer of the failure. This shall be done via the MD-DATA.confirm primitive with a status of NO\_ACK. + +###### 8.1.5.1.4.4 Random backoff + +If a singlecast MPDU with its ACK request subfield set to 1 or the corresponding ACK MPDU is lost or corrupted, the singlecast MPDU shall be retransmitted. The MAC layer collision avoidance mechanism prevents nodes from retransmitting at the same time. The random delay shall be calculated as a period in the interval *aMacMinRetransmitDelay* .. *aMacMaxRetransmitDelay*; Refer to Table 8-19. + +##### 8.1.5.1.5 Idle mode + +If the MLME is requested to set *macRxOnWhenIdle* to TRUE, the PHY shall enter RX mode and stay in RX mode when a frame has been transmitted (AL). This is achieved when the MLME issues the PLME-SET-TRX-STATE.request primitive with a state of RX\_ON. + +If the MLME is requested to set *macRxOnWhenIdle* to FALSE, the PHY shall disable its receiver when a frame has been transmitted. This is achieved by the MLME issuing the PLME-SET-TRX-STATE.request primitive with a state of TRX\_OFF. + +#### 8.1.5.2 Transmission scenarios + +Due to the imperfect nature of the radio medium, a transmitted frame does not always reach its intended Dst. Figures 8-23 to 8-25 illustrate three different data transmission scenarios: + +- **Successful transmission.** The originating MAC layer transmits the MPDU to the recipient via the PHY data service. The originating MAC layer waits for *aMacMinAckWaitDuration* symbols. The destination MAC layer receives the MPDU, returns an ACK MPDU, and passes the MPDU to the next higher layer. The originating MAC layer receives the ACK MPDU. The data transfer is now complete, and the originating MAC layer issues a success confirmation to the network layer. + + + +This sequence diagram illustrates a successful transmission scenario between four entities: Source network layer, Source MAC layer, Destination MAC layer, and Destination network layer. The interaction is as follows: 1. The Source network layer sends an MD-DATA.request (AckReq = 1) to the Source MAC layer. 2. The Source MAC layer transmits a Data frame (AckReq = 1) to the Destination MAC layer. 3. The Destination MAC layer receives the frame and sends an ACK back to the Source MAC layer. 4. The Source MAC layer receives the ACK and sends an MD-DATA.confirm (SUCCESS) to the Source network layer. 5. The Destination MAC layer also sends an MD-DATA.indication to the Destination network layer. A label 'G.9959(15)\_F8-23' is present at the bottom right. + +Sequence diagram for a successful transmission scenario. + +Figure 8-23 – Successful transmission scenario + +- **Lost MPDU.** The originating MAC layer transmits the MPDU to the recipient via the PHY data service. The originating MAC layer waits for *aMacMinAckWaitDuration* symbols. The Dst MAC layer does not receive the MPDU and therefore does not return an ACK MPDU. The timer of the originating MAC layer expires. The transmission has failed and the originator retransmits the MPDU. This sequence is repeated up to *aMacMaxFrameRetries* times. If transmissions fail a total of $(1 + aMacMaxFrameRetries)$ times, the originating MAC layer issues a failure confirmation to the network layer. + + + +This sequence diagram illustrates a lost MPDU scenario. The entities are Source network layer, Source MAC layer, Destination MAC layer, and Destination network layer. The interaction is as follows: 1. The Source network layer sends an MD-DATA.request to the Source MAC layer. 2. The Source MAC layer attempts to transmit a Data frame, but it is lost (indicated by an 'X'). 3. A retry mechanism occurs, labeled 'Retry frame transmission up to aMinFrameRetries times.', shown with a loop symbol. 4. Another Data frame is attempted and lost again (indicated by another 'X'). 5. After the retries, the Source MAC layer sends an MD-DATA.confirm (NO\_ACK) to the Source network layer. A label 'G.9959(15)\_F8-24' is present at the bottom right. + +Sequence diagram for a lost MPDU scenario. + +Figure 8-24 – Lost MPDU scenario + +- **LostAck MPDU.** The originating MAC layer transmits the MPDU to the recipient via the PHY data service. The originating MAC layer waits for *aMacMinAckWaitDuration* symbols. The destination MAC layer receives the MPDU, returns an ACK MPDU back to the originator, and passes the MPDU to the network layer. The originating MAC layer does not receive the ACK MPDU and its timer expires. The transmission has failed, and the originator retransmits the MPDU. If transmissions fail a total of $(1 + aMacMaxFrameRetries)$ times, the MAC layer issues a failure confirmation to the network layer. + + + +Sequence diagram illustrating the 'Lost ACK MPDU scenario'. It shows four entities: Source network layer, Source MAC layer, Destination MAC layer, and Destination network layer. The Source network layer sends an MD-DATA.request to the Source MAC layer. The Source MAC layer transmits a 'Data frame' to the Destination MAC layer. The Destination MAC layer receives the frame and sends an 'ACK' back to the Source MAC layer. However, the ACK is lost (indicated by a crossed-out arrow). The Source MAC layer then performs 'Retry frame transmission up to aMinFrameRetries times.' (indicated by a loop with a cross). After the retries, the Source MAC layer sends an 'MD-DATA.confirm (NO\_ACK)' back to the Source network layer. The Destination MAC layer also sends an 'MD-DATA.indication' to the Destination network layer. The diagram is labeled G.9959(15)\_F8-25. + +**Figure 8-25 – Lost ACK MPDU scenario** + +# 9 LLC layer specification + +In the OSI 7-layer stack, the LLC layer is the upper part of the data link layer (DLL). + +## 9.1 General + +The purpose of the LLC layer is to enable de-multiplexing of incoming MPDUs. The LLC layer shall not change the contents of the data link PDU (DLPDU) payload. + +The following DLI interfaces are defined, as shown in Figure 9-1: + +- DLI.6LoWPAN: Interface for IPv6 packets carried in 6LoWPAN frames +- DLI.Default: Interface for non-IP PDUs + + + +Diagram showing instances of the DLI interface. At the top, '6LoWPAN' and 'Default' are shown with dashed lines leading to a common horizontal dashed line labeled 'DLI' with an arrow pointing to it. Below this dashed line is a box labeled 'LLC'. The diagram is labeled G.9959(12)-Amd.1(13)\_F9-1. + +**Figure 9-1 – Instances of the DLI interface** + +The DLI.Default interface shall receive all traffic which is not explicitly targeting other instances of the DLI interface. + +## 9.2 Cascaded adaptation layer architecture + +One or more adaptation layers may be injected into the DLL between the MAC and LLC layers, as shown in Figure 9-2. Each adaptation layer serves a specific purpose, such as handling mesh routing, segmentation or security encryption. The function of an adaptation layer may be triggered by the presence of a routing header or specific DLPDU header values. Each adaptation layer shall implement the MLI interface on each of its interfaces. Each adaptation layer may modify or entirely discard an incoming MPDU. An adaptation layer shall transparently forward incoming MPDUs to the next layer in case the actual adaptation layer has no relevant function to perform. + + + +Figure 9-2: Ordering of adaptation layers. A vertical stack of six boxes representing network layers. From top to bottom: Link control (LLC), Encryption (SEC), Segmentation (SAR), Mesh routing (NWK), MAC, and PHY. The first four layers (LLC to NWK) are shaded gray. The last two (MAC and PHY) are white. To the right of the stack is the text 'G.9959(12)-Amd.1(13)\_F9-2'. Below the stack is a legend: a gray square for 'ITU-T G.9959 adaptation layer' and a white square for 'OSI layer'. + +**Figure 9-2 – Ordering of adaptation layers** + +## 9.3 DLPDU format + +The LLC receives an MPDU from the MLI interface. The MAC layer specifies MPDU formats for unicast and multicast transmission modes (see Figure 9-3). + + + +Figure 9-3: General MPDU format. A horizontal bar divided into three sections: 'MPDU header' (shaded), 'DLPDU' (white), and 'MPDU trailer' (shaded). Below the bar, a double-headed arrow labeled 'MSDU' spans the 'DLPDU' section. To the right of the bar is the text 'G.9959(15)\_F9-3'. + +**Figure 9-3 – General MPDU format** + +It is further specified that MPDUs may carry mesh routing information when the "Routed" flag of the frame control field is set or if the "Routed Frame" header type is used. In this case, a routing header is prepended to the DLPDU carried in the MSDU, as shown in Figure 9-4. + + + +Figure 9-4: MPDU format for routed frame. A horizontal bar divided into four sections: 'MPDU header' (shaded), 'Routing header' (white), 'DLPDU' (white), and 'MPDU trailer' (shaded). Below the bar, a double-headed arrow labeled 'MSDU' spans the 'Routing header' and 'DLPDU' sections. To the right of the bar is the text 'G.9959(15)\_F9-4'. + +**Figure 9-4 – MPDU format for routed frame** + +For correctly configured nodes, the LLC layer should never receive an MPDU which carries routing information. The LLC layer shall ignore an MPDU which carries routing information. The following text assumes that no routing header is prepended to the MPDU payload when it is received by the LLC layer. + +The DLPDU shall carry a DLPDU header, and may carry a payload field, as shown in Figure 9-5. The payload field may have any length up to *aLlcMaxDlpduSize* bytes. The payload field may carry another encapsulated DLPDU. + + + +Figure 9-5: DLPDU format. A horizontal bar divided into two sections: 'DLPDU header' (white) and 'Payload' (white). Above the 'DLPDU header' section is the text 'Bytes: 2/3'. Above the 'Payload' section is the text 'n'. Below the bar, a double-headed arrow labeled 'DLPDU' spans both sections. To the right of the bar is the text 'G.9959(12)-Amd.1(13)\_F9-5'. + +**Figure 9-5 – DLPDU format** + +### 9.3.1 DLPDU header + +The DLPDU header comprises two fields: the Command Class and the Command, as shown in Figure 9-6. + + + +Diagram of the DLPDU header structure. It shows two fields: 'Command Class' (1/2 bytes) and 'Command' (1 byte). A double-headed arrow below the fields is labeled 'DLPDU header'. The reference 'G.9959(12)-Amd.1(13)\_F9-6' is at the bottom right. + +**Figure 9-6 – DLPDU header** + +#### 9.3.1.1 Command Class + +The Command Class field may be 1 or 2 bytes in length. + +In the general case, the Command Class field shall be 1 byte long. If the first byte of the command class is a value in the range *aLlcFirstExtendedCommandClass1* .. *aLlcLastExtendedCommandClass1*, the DLPDU header contains an extended command class identifier. An extended Command Class field shall be 2 bytes in length. + +**Table 9-1 – Command class types** + +| Cmd Cls 1 | Cmd Cls 2 | Command class type | +|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------|--------------------| +| aLlcFirstNormalCommandClass1 ..
aLlcLastNormalCommandClass1 | (not present) | Normal | +| aLlcFirstExtendedCommandClass1 ..
aLlcLastExtendedCommandClass1 | aLlcFirstExtendedCommandClass2 ..
aLlcLastExtendedCommandClass2 | Extended | + +#### 9.3.1.2 Command + +The Command field shall be 1 byte in length and specifies one particular command for a given command class. + +## 9.4 Data link interface selection + +The LLC layer shall extract the DLPDU contained in an incoming MPDU and forward the DLPDU to a target DLI. The target DLI shall be determined by an evaluation of the DLPDU header Command Class field. + +### 9.4.1 DLI.IPv6 interface selection + +The LLC layer shall forward the DLPDU to the DLI.6LoWPAN interface if the DLPDU header Command Class field carries the 6LoWPAN command class identifier *aLlc6lowpanCommandClass*. + +### 9.4.2 DLI.Default interface selection + +Any DLPDU which does not match the explicit selection criterion for another DLI interface instance shall be forwarded to the DLI.Default interface. + +## 9.5 LLC layer constants + +This clause specifies the constants relating to the LLC layer. + +### 9.5.1 LLC constants + +The LLC shall comply with the constants defined in Table 9-2. + +**Table 9-2 – LLC constants** + +| Constants | Description | Value | +|---------------------------------------|-----------------------------------------------|------------| +| aLlcMaxDlpduSize | The maximum DLPDU size to support | 1350 bytes | +| aLlcFirstNormalCommandClass1 | Start of Normal command class range, byte 1 | 0x00 | +| aLlcLastNormalCommandClass1 | End of Normal command class range, byte 1 | 0xF0 | +| aLlcFirstExtendedCommandClass1 | Start of Extended command class range, byte 1 | 0xF1 | +| aLlcLastExtendedCommandClass1 | End of Extended command class range, byte 1 | 0xFF | +| aLlcFirstExtendedCommandClass2 | Start of Extended command class range, byte 2 | 0x00 | +| aLlcLastExtendedCommandClass2 | End of Extended command class range, byte 2 | 0xFF | +| aLlc6lowpanCommandClass | 6LoWPAN identifier indicating IPv6 payload | 0x4F | + +# 10 Adaptation layers + +As specified in clause 9 ("LLC layer specification"), one or more adaptation layers may be injected in between the MAC and LLC layers. + +## 10.1 SAR adaptation layer + +The SAR adaptation layer allows ITU-T G.9959 nodes to exchange long payloads. Examples of such payloads include security certificates for ITU-T G.9959 network bootstrapping or IPv6 packets. + + + +The diagram illustrates the SAR adaptation layer's segmentation process. A 'Sending node' on the left transmits a series of segments to a 'Receiving node' on the right. The first segment is labeled 'FirstSegment'. This is followed by eight segments labeled 'SubsequentSegment'. The final segment is labeled 'SegmentComplete'. The segments are shown as horizontal arrows pointing from left to right. The diagram is labeled 'G.9959(12)-Amd.1(13)\_F10-1' at the bottom right. + +Diagram showing the transfer of a datagram as segments from a sending node to a receiving node. The segments are labeled FirstSegment, SubsequentSegment (repeated 8 times), and SegmentComplete. The diagram is labeled G.9959(12)-Amd.1(13)\_F10-1. + +**Figure 10-1 – Example of datagram transferred as segments** + +### 10.1.1 Terminology overview + +The SAR adaptation layer provides segmentation and reassembly of a datagram by splitting up the datagram into segments, as shown in Figure 10-1, each of which fits into a MAC data payload (i.e., the MSDU). The datagram is formatted as a DLPDU with two header fields (Command Class, Command) like any other DLPDU. + +The SAR adaptation layer defines the transport service command class. As with all other command classes, the transport service command class is unconcerned whether segments are transported in direct range or by a mesh routing protocol. + +### 10.1.2 SAR adaptation layer specification + +The SAR adaptation layer shall provide the following features in order to obtain reliable data transfer of datagrams larger than the MSDU can accommodate. + +Typical examples are security encapsulated datagrams and 6LoWPAN encapsulated IPv6 packets. + +#### 10.1.2.1 Transparent functionality + +The SAR adaptation layer shall support segmentation and reassembly of any datagram up to *aLlcMaxDlPduSize* bytes. + +A node implementing the SAR adaptation layer shall automatically determine if a datagram fits into the available MPDU payload length. A node should not use segmentation if a datagram can be sent in one MPDU. + +#### 10.1.2.2 Relaxed transmission timing for long payloads + +In order not to congest the network, large data transfers shall leave transmit opportunities for other nodes in the network. If sending a command longer than *aSarRelaxedTimingMacFrames* MSDUs, a node shall implement a delay between every transmitted MSDU. The minimum required time delay and number of MSDUs before a delay shall be inserted depends on the actual data rate as follows: + +- Data rate R2: At least *aSarRelaxedTimingDelayR2* ms if sending more than *aSarRelaxedTimingMacFrames* MSDUs back-to-back; +- Data rate R3: At least *aSarRelaxedTimingDelayR3* ms if sending more than *aSarRelaxedTimingMacFrames* MSDUs back-to-back. + +#### 10.1.2.3 Varying PHY PDU size + +The available MPDU payload size depends on the actual bit rate. The SAR adaptation layer shall support all MSDU sizes offered by the actual MAC/PHY layer. The payload length available to SAR segments may be shorter than the MSDU sizes specified in Table 8-18 if additional headers, e.g., a routing header, are prepended by lower adaptation layers; refer to clause 9.2. + +#### 10.1.2.4 Segment re-transmission + +The segment reassembly process may end up missing a number of segments in the receive buffer, e.g., due to a checksum error. The receiving node shall be able to request the retransmission of individual segments to complement the segments already received. The algorithm shall be able to handle the case where retransmitted segments are also lost. If segments are received via broadcast or multicast transmission, the receiving node shall not request the retransmission of segments. + +#### 10.1.2.5 Robust error handling + +In case no segments are received in response to a retransmission request, a receiving node shall discard all segments previously received. + +If a sending node repeatedly fails to deliver a segment to a destination node, the node shall abort transmission of all remaining segments. + +### 10.1.3 The transport service command class + +The SAR adaptation layer shall use the transport service command class to transfer long datagrams between two nodes. The datagram shall start with two fields carrying a command class and command, refer to clause 9. + +#### 10.1.3.1 First segment command + +The first segment command initiates the transfer of a datagram, as shown in Figure 10-2. + + + +| | | | | | | | | +|-------------------------------------------------|---|---|-----|-------------------------|---|---|---| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| Command Class = COMMAND_CLASS_TRANSPORT_SERVICE | | | | | | | | +| Command = COMMAND_FIRST_SEGMENT | | | | datagram_size_1 [10..8] | | | | +| datagram_size_2 [7..0] | | | | | | | | +| Session ID | | | Ext | Reserved | | | | +| Header Extension Length (OPTIONAL) | | | | | | | | +| Header Extension (OPTIONAL) | | | | | | | | +| Payload 1 | | | | | | | | +| ... | | | | | | | | +| Payload N | | | | | | | | +| FCS 1 [15..8] | | | | | | | | +| FCS 2 [7..0] | | | | | | | | + +Figure 10-2 – Frame format of first segment command + +##### 10.1.3.1.1 Command (5 bits) + +The command field is reduced to a 5-bit field in order to limit the overhead introduced by the segment header. The LS 3 bits shall be masked out before decoding the command code when detecting the transport service command class. + +The command code shall be the 5-bit value *aSarFirstSegmentCommand*. + +##### 10.1.3.1.2 Datagram size (11 bits) + +Indicates the overall size of the datagram carried in the segments. The unit is 1 byte. Bit 0 is the least significant bit (LSB). The value shall not exceed *aLlcMaxDlpduSize* bytes. + +##### 10.1.3.1.3 Reserved (3 bits) + +This field shall be set to 0 by a sending node and shall be ignored by a receiving node. + +##### 10.1.3.1.4 Ext (1 bit) + +This field shall be used to indicate the presence of the header extension length and header extension fields. The field shall be set to 1 if there is a header extension. A receiving node shall ignore unsupported header extensions and process the command, skipping unsupported extensions. + +##### 10.1.3.1.5 Session ID (4 bits) + +This field identifies the session. The session ID shall be incremented when a new datagram transmission is initiated. A receiver shall verify the session ID of all received segments. Segments shall be discarded if an unknown session ID is detected. + +##### 10.1.3.1.6 Header extension length (8 bits) + +This field is only present if the Ext bit is set to 1. + +A sending node may add header extension fields to the command header. In this case, the Ext bit shall be set to 1 and the following fields shall be present in the command header: + +- Header extension length +- Header extension + +##### 10.1.3.1.7 Header extension (variable size) + +This field is only present if the Ext bit is set to 1. Refer to clause 10.1.3.1.4. + +##### 10.1.3.1.8 Payload (variable size) + +The payload field of a first segment shall carry the first segment of a datagram. + +A receiving node shall derive the size of the payload field from the size of entire command, subtracting all header fields as well as the checksum field. + +##### 10.1.3.1.9 FCS (16 bits) + +This field carries a CRC-16 FCS. The FCS shall be calculated using the CRC-16-CCITT mechanism with the following parameters: + +- Polynomial code shall be 0x1021 (*aSarFcsPolynomium*), representing the polynomial $x^{16} + x^{12} + x^5 + x^0$ ; +- CRC register shall be initialized to *aSarFcsInitValue* by the TX as well as receiver; +- The calculated CRC-16 value shall cover all fields of the first segment command except for the FCS fields; +- The calculated CRC-16 value shall not include padding after the frame, neither zeros nor any other value; +- The CRC-16 value shall be calculated one byte at a time in the transmission order, starting with the command class field; +- The most significant bit (MSB) of a byte shall be transmitted and received first, and likewise be the first to be processed in a serialized implementation; +- Bit 0 of the CRC-16 value corresponds to the input register of a serialized implementation of the CRC-16 calculation. Bit 0 is the LSB of the 16-bit word. + +A conceptual serial example is provided in Figure 10-3 below on how the polynomial $x^{16} + x^{12} + x^5 + x^0$ may be implemented. + + + +Transmitted first + +| | | | | | +|------|----------|----------|----------|-----| +| Byte | 1 | 2 | 3 | ... | +| | 01101011 | 10011101 | 01010110 | | +| bit | 7 | 0 | | | +| | (MS) | (LS) | | | + +G.9959(12)-Amd.1(13)\_F10-2 + +Figure 10-3: CRC-16 implementation example. The diagram shows a serial implementation of a CRC-16 calculator using three 16-bit shift registers and three XOR gates. The first register is initialized with the value 0x1021 (bits 15 and 12 set). The second register is initialized with the value 0x5555 (bits 11, 9, 7, 5, 3, 1 set). The third register is initialized with the value 0x0001 (bit 0 set). The output of the third register is the CRC-16 value. Below the diagram, a table shows the transmission of three bytes: Byte 1 (01101011), Byte 2 (10011101), and Byte 3 (01010110). The bits are transmitted from bit 7 (MSB) to bit 0 (LSB). + +Figure 10-3 – CRC-16 implementation example + +The following test vector shown in Figure 10-4 may be used for ensuring compliance with this Recommendation. + +| Test frame | CRC | +|----------------------------|-------| +| C2 A2 15 0D 03 03 02 0B 01 | 2C 66 | + +Figure 10-4 – CRC-16 implementation test vector + +#### 10.1.3.2 Subsequent segment command + +One or more subsequent segment commands follow the first segment command and carry the remaining part of the datagram. (See frame format shown in Figure 10-5.) + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | +|-------------------------------------------------|---|---|-----|---|---------------------------|---|---|--|--|--|--|--| +| Command Class = COMMAND_CLASS_TRANSPORT_SERVICE | | | | | | | | | | | | | +| Command = COMMAND_SUBSEQUENT_SEGMENT | | | | | datagram_size_1 [10..8] | | | | | | | | +| datagram_size_2 [7..0] | | | | | | | | | | | | | +| Session ID | | | Ext | | datagram_offset_1 [10..8] | | | | | | | | +| datagram_offset_2 [7..0] | | | | | | | | | | | | | +| Header extension length (OPTIONAL) | | | | | | | | | | | | | +| Header extension (OPTIONAL) | | | | | | | | | | | | | +| Payload 1 | | | | | | | | | | | | | +| ... | | | | | | | | | | | | | +| Payload N | | | | | | | | | | | | | +| FCS 1 [15..8] | | | | | | | | | | | | | +| FCS 2 [7..0] | | | | | | | | | | | | | + +Figure 10-5 – Frame format of subsequent segment command + +Receiving the last segment of a singlecast datagram, the receiving node shall return either a segment request command or a segment complete command. The receiving node shall not respond to a broadcasted datagram. + +##### 10.1.3.2.1 Command (5 bits) + +The command code shall be the 5-bit value *aSarSubsequentSegmentCommand*. + +##### 10.1.3.2.2 Datagram size (11 bits) + +Refer to clause 10.1.3.1.2. + +##### 10.1.3.2.3 Ext (1 bit) + +Refer to clause 10.1.3.1.4. + +##### 10.1.3.2.4 Session ID (4 bits) + +Refer to clause 10.1.3.1.5. + +##### 10.1.3.2.5 Datagram offset (11 bits) + +This field indicates the offset to apply to this segment when reassembling the datagram in the receive buffer. The unit is 1 byte. Bit 0 is the LSB. + +##### 10.1.3.2.6 Header extension length (8 bits) + +This field is only present if the Ext bit is set to 1. + +Refer to clause 10.1.3.1.6. + +##### 10.1.3.2.7 Header extension (variable size) + +This field is only present if the Ext bit is set to 1. + +Refer to clause 10.1.3.1.7. + +##### 10.1.3.2.8 Payload (variable size) + +The payload field of a subsequent segment may carry any portion of a datagram. + +A receiving node shall derive the size of the payload field from the size of entire command, subtracting all header fields as well as the checksum field. + +##### 10.1.3.2.9 Frame check sequence (16 bits) + +Refer to clause 10.1.3.1.9. + +#### 10.1.3.3 Segment request command + +The segment request command may be used by a receiving node to request a missing segment. (See frame format shown in Figure 10-6.) Multiple missing segments should be requested one at a time. + +This message shall not be used in response to segments received via broadcast or multicast. + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-------------------------------------------------|---|---|-----------------|---|---------------------------|---|---| +| Command Class = COMMAND_CLASS_TRANSPORT_SERVICE | | | | | | | | +| Command = COMMAND_SEGMENT_REQUEST | | | | | reserved | | | +| Session ID | | | reserved | | datagram_offset_1 [10..8] | | | +| datagram_offset_2 [7..0] | | | | | | | | + +Figure 10-6 – Frame format of segment request command + +##### 10.1.3.3.1 Command (5 bits) + +The command code shall be the 5-bit value *aSarSegmentRequestCommand*. + +##### 10.1.3.3.2 Reserved + +This field shall be set to 0 by a sending node and shall be ignored by a receiving node. + +##### 10.1.3.3.3 Session ID (4 bits) + +Refer to clause 10.1.3.1.5. + +##### 10.1.3.3.4 Datagram offset + +Refer to clause 10.1.3.2.5. + +#### 10.1.3.4 Segment complete command + +The Segment complete command shall be returned from the receiving node when all segments have been correctly received. (See frame format shown in Figure 10-7.) + +This message shall not be used in response to segments received via broadcast or multicast. + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-------------------------------------------------|---|---|-----------------|---|-----------------|---|---| +| Command Class = COMMAND_CLASS_TRANSPORT_SERVICE | | | | | | | | +| Command = COMMAND_SEGMENT_COMPLETE | | | | | reserved | | | +| Session ID | | | reserved | | | | | + +Figure 10-7 – Frame format of segment complete command + +##### 10.1.3.4.1 Command (5 bits) + +The command code shall be the 5-bit value *aSarSegmentCompleteCommand*. + +##### 10.1.3.4.2 Reserved + +This field shall be set to 0 by a sending node and shall be ignored by a receiving node. + +##### 10.1.3.4.3 Session ID (4 bits) + +Refer to clause 10.1.3.1.5. + +#### 10.1.3.5 Segment wait command + +The segment wait command may be returned in response to a first segment command or a subsequent segment command by a node which is already receiving segments from another node. (See frame format shown in Figure 10-8.) + +This message shall not be used in response to segments received via broadcast or multicast. + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-------------------------------------------------|---|---|---|---|-----------------|---|---| +| Command class = COMMAND_CLASS_TRANSPORT_SERVICE | | | | | | | | +| Command = COMMAND_SEGMENT_WAIT | | | | | Reserved | | | +| Pending segments | | | | | | | | + +Figure 10-8 – Frame format of segment wait command + +##### 10.1.3.5.1 Command (5 bits) + +The command code shall be the 5-bit value *aSarSegmentWaitCommand*. + +##### 10.1.3.5.2 Reserved + +This field shall be set to 0 by a sending node and shall be ignored by a receiving node. + +##### 10.1.3.5.3 Pending segments (8 bits) + +The value indicates the number of segments not yet received by the receiving node. Since the delivery time of any segment depends on path length (direct vs. 5 hop routing), the value does not represent an absolute time. Furthermore, the node currently sending may initiate another transfer immediately after the completion of the actual segmented datagram. + +A sending node shall stop sending segments for a minimum period of $(100 \text{ ms} \times [\text{number of pending segments}])$ if receiving a segment wait command. When resuming transmission, the sending node shall restart segment transmission with the first segment command. + +#### 10.1.3.6 Managing segment transfer and handling exceptions + +The following clauses present the mechanisms for handling segments and exceptions such as missing segments. + +##### 10.1.3.6.1 Avoiding concurrent peer-to-peer transfers + +The SAR adaptation layer shall not allow other multi-MSDU datagrams to be transmitted to any destination node before the ongoing transmission of one multi-MSDU datagram has been completed. Doing so could delay the datagram transmission, causing security timers to timeout. While the SAR adaptation layer is transmitting a datagram to a given destination, the SAR adaptation layer may transmit a single-MSDU command to another destination node. + +A receiving node may return a segment wait command in response to a singlecast segment if the node is already receiving another segmented datagram. + +##### 10.1.3.6.2 Completing the transfer (receiving node) + +A receiving node shall return a segment complete command if all segments have been received. A segment request command shall be returned if the receiving has timed out waiting for segments. + +The receiving node shall wait the following time after the reception of a segment before requesting missing segments: + +- Data rate R2: at least *aSarTransferTimeoutR2* +- Data rate R3: at least *aSarTransferTimeoutR3* + +If the datagram is broadcasted, the node shall drop already received segments and shall not send a segment request command. + +##### 10.1.3.6.3 Completing the transfer (sending node) + +When a sending node has completed transmission of a datagram, the sending node shall wait for a segment complete message from the receiving node. Depending on the transmission speed, the sending node shall wait the following time before sending another datagram if no segment complete message is received: + +- Data rate R2: at least *aSarSegmentCompleteTimeoutR2* +- Data rate R3: at least *aSarSegmentCompleteTimeoutR3* + +As retransmission is provided by the MAC layer, the sending node shall not retransmit the last segment in case of a timeout. + +##### 10.1.3.6.4 Tie-breaking + +In a special case, two nodes may start sending segments at the same time. The following algorithm shall be used to avoid a deadlock situation where both nodes consistently send Wait messages to the other node. + +A receiving node which is already transmitting segments should perform a tie-breaking check before dropping an incoming segment. If the tie-breaking check is positive, the receiving node should accept the incoming segment and abort the ongoing transmission. The tie-break check is positive if the following three conditions are all met: + +1. The receiving node is currently transmitting a datagram. +2. The recipient of the datagram being transmitted is also the originator of the received segment +3. The receiving node has a lower NodeID than the originator. + +### 10.1.4 SAR adaptation layer constants + +This clause specifies the constants relating to the SAR adaptation layer. + +#### 10.1.4.1 SAR constants + +The SAR shall comply with the constants defined in Table 10-1. + +**Table 10-1 – SAR constants** + +| Constants | Description | Value | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------|----------| +| aSarRelaxedTimingMacFrames | Use relaxed transmission timing if sending SAR datagrams longer than aSarRelaxedTimingFrameCount MPDUs. | 2 frames | +| aSarRelaxedTimingDelayR2 | Delay between each frame at data rate R2 when using relaxed transmission timing | 35 ms | +| aSarRelaxedTimingDelayR3 | Delay between each frame at data rate R3 when using relaxed transmission timing | 15 ms | +| aSarTransferTimeoutR2 | Waiting time before requesting a missing segment at data rate R2 | 800 ms | +| aSarTransferTimeoutR3 | Waiting time before requesting a missing segment at data rate R3 | 400 ms | +| aSarSegmentCompleteTimeoutR2 | Waiting time before sending another datagram at data rate R2 | 1000 ms | + +**Table 10-1 – SAR constants** + +| Constants | Description | Value | +|-------------------------------------|--------------------------------------------------------------|--------------| +| aSarSegmentCompleteTimeoutR3 | Waiting time before sending another datagram at data rate R3 | 500 ms | +| aSarTransportServiceCc | Transport service command class identifier | 0x55 | +| aSarFirstSegmentCommand | Transport service first segment identifier | 0x18 | +| aSarSubsequentSegmentCommand | Transport service subsequent segment identifier | 0x1C | +| aSarSegmentRequestCommand | Transport service segment request identifier | 0x19 | +| aSarSegmentCompleteCommand | Transport service segment complete identifier | 0x1D | +| aSarSegmentWaitCommand | Transport service segment wait identifier | 0x1E | +| aSarFcsPolynomium | FCS polynomium defined as $x^{16} + x^{12} + x^5 + x^0$ | 0x1021 | +| aSarFcsInitValue | FCS init value | 0x1D0F | + +# Annex A + +# Non-radio related aspects of the Z-Wave PHY and MAC Specifications + +(This annex forms an integral part of this Recommendation.) + +## A.1 Introduction + +### A.1.1 General + +Z-Wave is a low-power, low-cost wireless technology enabling consumer-grade products with networked features. Examples include remote controlled light dimmers, networked temperature sensors, electronic door locks and AV systems. + +This annex presents the physical (PHY) layer to be implemented by a device operating in a Z-Wave network. + +Low-power wireless radio networks suffer from frequent frame drops due to fading effects, spurious noise and reflections. Z-Wave provides low-level retransmissions to recover from such situations. Network layers may employ mesh routing to extend networks beyond what is possible in direct range. The Z-Wave routing protocol is one such example. + +### A.1.2 Technology overview + +NOTE – The information in this clause is for informational purposes only and contains features that are out of scope of this Recommendation. + +The Z-Wave framework incorporates its own network, transport, and application layers. These should not be confused with the OSI layers or the network and transport layers defined by the IETF for IP transport. The Z-Wave framework supports IP transport as well as IP routing protocols. + +Nodes receive a unique NodeID during network inclusion. A network may hold up to 232 nodes. A HomeID is used to identify a specific domain. HomeID and NodeID are auto-configured with no user intervention. + +The Z-Wave network layer defines the Z-Wave routing protocol which is a source routing protocol. The Z-Wave routing protocol allows an originator to reach a destination node via one or more repeaters. A reactive discovery algorithm allows originators to determine new source routes when required. + +Z-Wave uses a special frame format for multicast messages. The Z-Wave multicast frame header carries a complete destination bit map in the frame header. + +The Z-Wave application layer defines a wide range of device and command classes for various devices such as lamps, door locks and temperature sensors. + +## A.2 General description + +The Z-Wave PHY layer defines modulation schemes, data rates, synchronization methods and a frame format for use in low-power, low-bandwidth control networks. + +The Z-Wave MAC layer defines a half duplex protocol for acknowledged wireless communication in a low-cost control network. The MAC layer targets "soft" real-time applications which are not time critical in nature. The MAC layer supports on-demand communication to battery operated nodes. + +The PHY layer is responsible for the following tasks: + +- assignment of RF profiles to physical channels; +- activation and deactivation of the radio TRX; +- transmission and reception; + +- clear channel assessment; +- frequency selection; +- link quality assessment for received frames. + +A Z-Wave TRX can operate in a one, two or three channel configuration in license-free RF bands. + +The MAC is responsible for handling the following: + +- HomeID assignment; +- NodeID assignment; +- collision avoidance algorithm; +- backoff algorithm; +- automatic retransmission in case of transmission errors; +- support for battery operation. + +MAC frames carry one small header in order to conserve bandwidth. While presented as one header, a few fields are used by higher layers. These fields are carried transparently and ignored by the MAC layer. + +The Z-Wave routing protocol is out of scope of this Recommendation. + +### A.2.1 Network topology + +#### A.2.1.1 Network components + +Z-Wave nodes can be divided into two subgroups: normal nodes; and low-power nodes. The normal nodes are typically in receive mode at all times. The low-power nodes spend the majority of the operating life in power down and wake up at regular short intervals to minimize power consumption. + +#### A.2.1.2 Network topology + +NOTE – The network formation is handled by the network layer, which is out of the scope of this Recommendation. However, this clause provides a brief overview of how the supported network topology is formed. + +In a mesh network topology, each device is capable of communicating with devices within direct range. A node can send and receive messages and can also relay messages for its neighbours. Introducing routing provides for a redundant and more reliable network. An example of a mesh network is shown in Figure A.1. + + + +The diagram illustrates a mesh network topology with 10 Z-Wave nodes, represented by green circles. The nodes are interconnected by dashed lines, forming a mesh. A legend at the bottom left shows a green circle labeled "Z-Wave node". The diagram is labeled "G.9959(15)\_FA.1" at the bottom right. + +Diagram of a mesh network topology showing 10 Z-Wave nodes connected in a mesh. A legend indicates a green circle represents a Z-Wave node. The diagram is labeled G.9959(15)\_FA.1. + +**Figure A.1 – Mesh network topology** + +Routes may be established on a proactive basis or via on-demand discovery. If messages are lost due to fading effects and/or interference, the node may retransmit messages and if still failing, use alternative routes. New alternative routes may be discovered if needed. + +#### A.2.1.3 Bootstrapping + +A unique 32-bit identifier called the HomeID is used to identify individual domains. + +NodeIDs are unique within a given domain. A NodeID is an 8-bit short address. The first node hands out the HomeID and unique NodeIDs to all other nodes added to the domain. + +### A.2.2 Network architecture + +The Z-Wave architecture is defined in terms of layers. Each layer is responsible for one part of the operation and offers services to the higher layers: a data entity provides a data transmission service; and a management entity provides other services related to the actual layer. The data and management entities define the logical links between the layers. + +A Z-Wave node implements the PHY layer, which contains the RF TRX along with its low-level control mechanism, a MAC layer that provides access to the physical channel for all types of transfers, a network layer controlling message routing, and a combined application layer that collapses the OSI stack layers transport, session, and presentation. + +Figure A.2 shows these layers in a graphical representation. + + + +The diagram illustrates the Z-Wave protocol stack. At the top is the Application layer, which is further divided by a dashed horizontal line into the 'Application layer' and the 'Application interface sublayer (AIS)'. Below the Application layer is the Network layer. Below the Network layer is the MAC layer, which is shaded grey. Below the MAC layer is the PHY layer, also shaded grey. At the bottom is the Physical Medium, represented by an oval. Double-headed vertical arrows connect each layer to the one below it. A long vertical double-headed arrow on the right side of the stack, spanning from the Application layer down to the PHY layer, is labeled 'Z-Wave'. + +Diagram of Z-Wave layers showing a stack of five layers: Application layer (top), Network layer, MAC layer, PHY layer, and Physical Medium (bottom). The Application layer is divided into 'Application layer' and 'Application interface sublayer (AIS)' by a dashed line. The MAC and PHY layers are shaded grey. A vertical double-headed arrow on the right side spans from the Application layer to the PHY layer and is labeled 'Z-Wave'. + +Figure A.2 – Z-Wave layers + +This annex specifies the PHY and MAC layers. Upper layers are outside the scope of this Recommendation. + +#### A.2.2.1 PHY layer + +The features of the PHY are activation and deactivation of the RF TRX, frequency selection, and transmitting as well as receiving frames. The RF receiver is able to perform a clear channel assessment. The RF TRX operates in a one, two, or three-channel configuration located in the license-free ISM frequency bands. + +The PHY provides two services: (1) the PD service accessed through the PD-SAP; and (2) the PHY management service interfacing with the physical layer management entity service access point (PLME-SAP). The PD service enables the transmission and reception of PPDUs across the physical radio channel. + +Clause A.3 contains the full specifications of the PHY layer. + +#### A.2.2.2 MAC layer + +The features of the MAC layer are channel access, frame validation, acknowledged frame delivery, and retransmissions. + +The MAC layer provides two services: the MAC data service, accessed through the MD-SAP, and the MAC management service interfacing with the MAC layer management entity service access point (MLME-SAP). The MAC data service enables the transmission and reception of MPDUs across the PD service. + +Clause A.4 contains the full specifications of the MAC layer. + +### A.2.3 Functional overview + +A brief overview of the general functions of a Z-Wave network is given in the following clauses and includes information on the data transfer model, the frame structure, robustness and power consumption considerations. + +#### A.2.3.1 MPDU formats + +A number of MAC PDU formats are defined. + +Figure A.3 shows the structure of the general MPDU. The MAC service data unit (MSDU) carries the payload data from the network layer. The MSDU is prepended with a MAC header (MHR) and appended with a MAC footer (MFR). The MHR, MSDU, and MFR together constitute the MAC protocol data unit (PDU). + + + +Bytes: 4 1 2 1 k n 1/2 + +**MAC layer** + +| | | | | | | | +|--------|----------------|---------------|--------|---------------------|--------------|-----| +| HomeID | Source node ID | Frame control | Length | Destination node ID | Data payload | FCS | +| MHR | | | | | MSDU | MFR | + +MPDU + +**PHY layer** + +| | | | | +|-------------------|--------------------------|--------------|------------------------| +| Preamble sequence | Start of frame delimiter | Data payload | End of frame delimiter | +| | | PSDU | | + +PPDU + +\*R1 only + +n 1/2 + +**MAC layer** + +| | | | +|------------|------------------|-----| +| MAC header | MAC data payload | FCS | +| MHR | MSDU | MFR | + +MPDU + +**PHY layer** + +| | | | +|------------|------------------|------------------------| +| PHY header | PHY data payload | End of frame delimiter | +| | PSDU | | + +PPDU + +G.9959(15)\_FA.3 + +Figure A.3 – General MPDU structure. The diagram shows two versions of the MPDU structure. The top version shows the MAC layer with fields: HomeID (4 bytes), Source node ID (1 byte), Frame control (2 bytes), Length (1 byte), Destination node ID (k bytes), Data payload (n bytes), and FCS (1/2 bytes). The first four fields form the MAC Header (MHR), the fifth is the start of the MAC Service Data Unit (MSDU), and the last is the MAC Footer (MFR). The entire MAC PDU is passed to the PHY layer as a PHY Service Data Unit (PSDU), which is then encapsulated in a PHY Protocol Data Unit (PPDU) with a Preamble sequence, Start of frame delimiter, and End of frame delimiter. A note indicates the FCS is '\*R1 only'. The bottom version shows a simplified MAC layer with a MAC header (MHR), MAC data payload (MSDU), and FCS (MFR). This is also passed to the PHY layer as a PSDU and encapsulated in a PPDU with a PHY header and End of frame delimiter. A note indicates the FCS is '1/2' bytes. Both diagrams show the MPDU spanning from the start of the MHR to the end of the MFR. + +Figure A.3 – General MPDU structure + +The MPDU is passed to the PHY layer as a PHY layer data unit (PSDU). The PSDU is prefixed with a start header (SHR) and an end header (EHR). + +##### **A.2.3.1.1 Singlecast MPDU** + +The singlecast MPDU uses the general frame structure (Figure A.3). + +##### **A.2.3.1.2 ACK MPDU** + +The ACK MPDU uses the general MPDU structure (Figure A.3). The MSDU may have a length of zero bytes. + +##### **A.2.3.1.3 Multicast MPDU** + +A dedicated Z-Wave multicast header explicitly identifies each target node via a dedicated multicast addressing bitmask. + +#### **A.2.3.2 Network robustness** + +The Z-Wave protocol employs various mechanisms to ensure robustness in the data transmission. These mechanisms of the MAC layer are backoff algorithm, frame ACK, data verification, and frame retransmission. + +##### **A.2.3.2.1 Clear channel assessment** + +A node shall query the availability of the channel from the PHY layer before transmitting. If the channel is found to be idle, the node may transmit its data. If the channel is found busy, the node shall wait for idle channel before transmitting. + +##### **A.2.3.2.2 Acknowledgment** + +A successful reception and validation of an MPDU may be confirmed with an ACK MPDU. If the Dst node receives an MPDU containing bit errors, the message shall not be acknowledged. An ACK request may be carried in the frame that needs ACK. + +##### **A.2.3.2.3 Retransmission** + +If two or more nodes transmit MPDUs simultaneously a collision may occur and the MPDUs may not reach their destinations. + +If the source node does not receive an ACK, it assumes that the transmission was unsuccessful and retries the MPDU transmission up to *aMacMaxFrameRetries* times. + +In order to avoid another collision each TX shall delay a retransmission by a random delay. + +##### **A.2.3.2.4 Multi-hop routing** + +The MAC layer defines MPDU header fields for support of multi-hop routing. Routing is outside the scope of this Recommendation. + +##### **A.2.3.2.5 Data validation** + +An 8-bit non-correcting FCS mechanism is employed to detect bit errors for data rates R1 and R2. A 16-bit non-correcting FCS mechanism is employed to detect bit errors for data rate R3. Refer to clause A.3.1.3 for details on data rates. + +#### **A.2.3.3 Power consumption considerations** + +One category of battery-powered nodes spend most of their operational life in a sleep mode. Such nodes may periodically wake up and poll other nodes to get pending messages. The PHY layer AL mode is used for listening during wake-up polling. + +Other low-power nodes may require a more responsive behaviour than can be achieved via periodic wake-up. Such nodes may use the PHY FL mode for incoming messages. + +##### A.2.3.3.1 Communication with a FLN + +Battery-powered devices may need to be reachable at any time. Nodes that are listening at regular intervals are said to operate in FL mode. The PHY layer provides an extended preamble sequence that allows an FL node to operate at a very low duty cycle while still being reachable. + +### A.2.4 Concept of primitives + +This clause provides a brief overview of the concept of service primitives (operations). Refer to [b-ITU-T X.210] for more detailed information. + +The services of a layer are the capabilities it offers to the user in the next higher layer or sublayer by building its functions on the services of the next lower layer. This concept is illustrated in Figure A.4, showing the service hierarchy and the relationship of the two correspondent N-users and their associated N-layer (or sublayer) peer protocol entities. + + + +The diagram shows the interaction between two Service users (N-user) and a Service provider (N-layer). A vertical arrow on the left indicates the flow of Time. The interaction consists of four primitives: Request (from N-user to N-layer), Indication (from N-layer to N-user), Response (from N-user to N-layer), and Confirm (from N-layer to N-user). The diagram is labeled G.9959(15)\_FA.4. + +Diagram illustrating service primitives between two Service users (N-user) and a Service provider (N-layer). A vertical arrow on the left indicates the flow of Time. The interaction consists of four primitives: Request (from N-user to N-layer), Indication (from N-layer to N-user), Response (from N-user to N-layer), and Confirm (from N-layer to N-user). The diagram is labeled G.9959(15)\_FA.4. + +Figure A.4 – Service primitives + +The services are specified by describing the information flow between the N-user and the N-layer. This information flow is modelled by discrete, instantaneous events, which characterize the provision of a service. Each event consists of passing a service primitive from one layer to the other through a SAP associated with an N-user. Service primitives convey the required information by providing a particular service. These service primitives are an abstraction because they specify only the provided service rather than the means by which it is provided. This definition is independent of any other interface implementation. + +Services are specified by describing the service primitives and parameters that characterize it. A service may have one or more related primitives that constitute the activity that is related to that particular service. Each service primitive may have zero or more parameters that convey the information required to provide the service. + +A primitive can be one of four generic types: + +- Request: the request primitive is passed from the N-user to the N-layer to request that a service is initiated; +- Indication: the indication primitive is passed from the N-layer to the N-user to indicate an internal N-layer event that is significant to the N-user. This event may be logically related to a remote service request, or it may be caused by an N-layer internal event; +- Response: the response primitive is passed from the N-user to the N-layer to complete a procedure previously invoked by an indication primitive; +- Confirm: the confirm primitive is passed from the N-layer to the N-user to convey the results of one or more associated previous service requests. + +## A.3 Physical (PHY) layer specification + +This clause specifies the PHY. The PHY is responsible for the following tasks: + +- Assignment of an RF profile to a physical channel; +- Activation and deactivation of the radio TRX; +- Data transmission and reception; +- clear channel assessment; +- Frequency selection; +- Link quality for received frames. + +Constants and attributes that are specified and maintained by the PHY are written in the text of this clause in *italics*. Constants have a general prefix of "a", e.g., *aPhyMaxFrameSizeRx*, and are listed in Table A.27. Attributes have a general prefix of "phy", e.g., *phyCurrentChannel*, and are listed in Table A.28. + +### A.3.1 TRX front end specifications + +This clause specifies requirements of the PHY. + +The Z-Wave specification shall conform to established regulations in Europe, United States, and other world regions. + +#### A.3.1.1 RF profiles + +An RF profile defines one or more data rates for use in a given radio channel. The definition of specific regional frequencies is outside the scope of this Recommendation. + +The list of RF profiles is specified in Table A.1. A TRX shall support up to 3 radio channels, each characterized by an RF profile. Each channel shall have a unique RF profile assigned to it. Depending on the actual region, RF Profiles may allow communication at one or more data rates and one or more channels. + +**Table A.1 – RF profiles** + +| RF profile | Region | Channel configurations | Centre frequency | R3 | R2 | R1 | FL (Note) | +|------------|---------------------------|------------------------|-------------------------|----|----|----|-----------| +| 0 | n/a | | n/a | | | | | +| 1 | European Union | 1,2 | fEU1 | √ | | | | +| 2 | | | fEU2 | | √ | √ | | +| 3 | | | fEU2 | | √ | | √ | +| 4 | United States | 1,2 | fUS1 | √ | | | | +| 5 | | | fUS2 | | √ | √ | | +| 6 | | | fUS2 | | √ | | √ | +| 7 | Hong Kong | 1,2 | fHK1 | √ | | | | +| 8 | | | fHK1 | | √ | √ | | +| 9 | | | fHK1 | | √ | | √ | +| 10 | Australia and New Zealand | 1,2 | fANZ1 | √ | | | | +| 11 | | | fANZ2 | | √ | √ | | +| 12 | | | fANZ2 | | √ | | √ | +| 13 | Malaysia | 1,2 | fMY1 | √ | | | | +| 14 | | | fMY1 | | √ | √ | | + +**Table A.1 – RF profiles** + +| RF profile | Region | Channel configurations | Centre frequency | R3 | R2 | R1 | FL (Note) | +|------------|--------|------------------------|------------------|----|----|----|-----------| +| 15 | | | $f_{MY1}$ | | √ | | √ | +| 16 | India | 1,2 | $f_{IN1}$ | √ | | | | +| 17 | | | $f_{IN1}$ | | √ | √ | | +| 18 | | | $f_{IN1}$ | | √ | | √ | +| 19 | Japan | 3 | $f_{JP1}$ | √ | | | √ | +| 20 | | | $f_{JP2}$ | √ | | | √ | +| 21 | | | $f_{JP3}$ | √ | | | √ | +| 22 | Israel | 1,2 | $f_{IL1}$ | √ | | | | +| 23 | | | $f_{IL1}$ | | √ | √ | | +| 24 | | | $f_{IL1}$ | | √ | | √ | +| 25 | Korea | 3 | $f_{KR1}$ | √ | | | √ | +| 26 | | | $f_{KR2}$ | √ | | | √ | +| 27 | | | $f_{KR3}$ | √ | | | √ | +| 28 | Russia | 1,2 | $f_{RU1}$ | √ | | | | +| 29 | | | $f_{RU1}$ | | √ | √ | | +| 30 | | | $f_{RU1}$ | | √ | | √ | +| 31 | China | 1,2 | $f_{CN1}$ | √ | | | | +| 32 | | | $f_{CN1}$ | | √ | √ | | +| 33 | | | $f_{CN1}$ | | √ | | √ | + +NOTE – FL mode is only applicable for the indicated RF profiles. AL mode may be used with any RF profile. + +#### A.3.1.2 Transmit frequency error + +Frequency error is defined as the difference between the measured transmitted centre frequency and the actual regional centre frequency. + +The frequency error shall not exceed $\pm 27$ ppm. + +#### A.3.1.3 Data rates + +The PHY shall support the data rates and the accuracy as listed in the table below. + +**Table A.2 – Data rate and data rate accuracy** + +| Data rate | Bit rate | Symbol rate | Accuracy | +|-----------|------------|-------------|--------------| +| R1 | 9.6 kbit/s | 19.2 kbaud | $\pm 27$ ppm | +| R2 | 40 kbit/s | 40 kbaud | $\pm 27$ ppm | +| R3 | 100 kbit/s | 100 kbaud | $\pm 27$ ppm | + +#### A.3.1.4 Channel configuration + +A compliant node shall operate in one of the three possible configurations as listed in the table below. + +**Table A.3 – Channel configurations** + +| Configuration | Num channels | Data rate | | | +|---------------|--------------|----------------------|------|------| +| | | R3 | R2 | R1 | +| 1 | 1 | – | Ch B | Ch B | +| 2 | 2 | Ch A | Ch B | Ch B | +| 3 | 3 | Ch A
Ch B
Ch C | – | – | + +Tables A.1 and A.3 shall be used in combination. + +Example: + +A node intended for the EU region may use configuration 2 which provides two alternative communication channels. The following RF profiles are available: + +- RF profile 1 at the frequency $f_{EU1}$ (Ch A) supporting data rate R3 in AL mode only; +- RF profile 2 at the frequency $f_{EU2}$ (Ch B) supporting data rates R1 and R2 in AL mode only; +- RF profile 3 at the frequency $f_{EU2}$ (Ch B) supporting data rate R2 in AL and FL mode. + +This imaginary node runs on battery but has to support low-latency communication. Thus, FL mode is preferred. When listening or transmitting to other FL nodes, the node uses RF Profile 3 (Ch B). When sending to AL nodes, the node uses RF Profile 1 (Ch A) or RF Profile 2 (Ch B). + +#### A.3.1.5 Modulation and encoding + +The PHY shall employ FSK for RF modulation at data rates R1 and R2. The PHY shall employ GFSK for RF modulation at data rates R3. + +Manchester code shall be used for data symbol encoding at data rate R1 and non-return-to-zero (NRZ) shall be used for data symbol encoding at data rates R2 and R3. + +The modulation and the coding format are summarized in Table A.4. + +**Table A.4 – Modulation and coding format** + +| Data Rate | Modulation | Coding | Frequency offset | Separation | Symbols | +|-----------|----------------|------------|------------------|-------------------|---------| +| R1 | FSK | Manchester | 20 kHz | 40 kHz $\pm 20\%$ | Binary | +| R2 | FSK | NRZ | 0 kHz | 40 kHz $\pm 20\%$ | Binary | +| R3 | GFSK, BT = 0.6 | NRZ | 0 kHz | 58 kHz $\pm 20\%$ | Binary | + +The mapping of NRZ symbols to the physical medium is given in Table A.5. + +**Table A.5 – NRZ symbol mapping** + +| Symbol | Frequency | +|--------|----------------------------------------| +| 0 | $f_{center\ frequency} + separation/2$ | +| 1 | $f_{center\ frequency} - separation/2$ | + +The mapping of Manchester symbols to the physical medium is given in Table A.6 below. + +**Table A.6 – Manchester symbol mapping** + +| Symbol | Frequency | +|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Transition from $(f_{\text{center frequency}} + f_{\text{offset}} - \text{separation}/2)$ to $(f_{\text{center frequency}} + f_{\text{offset}} + \text{separation}/2)$ | +| 1 | Transition from $(f_{\text{center frequency}} + f_{\text{offset}} + \text{separation}/2)$ to $(f_{\text{center frequency}} + f_{\text{offset}} - \text{separation}/2)$ | + +Table A.6 refers to a frequency offset, $f_{\text{offset}}$ . The frequency offset is specified in Table A.4. + +#### A.3.1.6 RF power measurement + +Unless stated otherwise, all RF power measurements, either transmit or receive, shall be made at the antenna connector. The measurements shall be made with equipment that is either matched to the impedance of the antenna connector or corrected for any mismatch. For devices without an antenna connector, the measurements shall be interpreted as EIRP (i.e., a 0 dBi gain antenna); and any radiated measurements shall be corrected to compensate for the antenna gain in the implementation. + +#### A.3.1.7 Transmit power adjustments (conducted) + +The TX output power level shall conform to local regulations. The output power level allowed by local regulations is denoted as "nominal". Actual absolute power levels are out of scope of this Recommendation. + +The TX shall be able to adjust its output power in steps of 2 dB in the range between the nominal transmit power down to (nominal output power – 10 dB). + +The TX shall further be able to reduce its output power to at least (nominal output power – 20 dB). + +#### A.3.1.8 Receiver sensitivity + +The receiver shall be of receiving a standard test frame at a minimum power level. + +The minimum receiver sensitivity for each data rate shall be as specified in Table A.8. + +The standard test frame and test conditions shall be as specified in Table A.7. + +**Table A.7 – Standard test frame** + +| Term | Definition | Conditions | +|----------------------|---------------------------------------------------------|------------------------------------------------------------------------------| +| Standard Test Frame | PHY frame used for testing sensitivity | PHY frame with at least four bytes of random payload data | +| FER | Average frame loss | Average measured over standard test frames | +| Receiver sensitivity | Threshold input signal power that yields a specific FER | FER < 1%.
Power measured at antenna terminals
Interference not present | + +**Table A.8 – Minimum receiver sensitivity** + +| Bit rate | Minimum receiver sensitivity | +|----------|------------------------------| +| R1 | –95 dBm | +| R2 | –92 dBm | +| R3 | –89 dBm | + +#### A.3.1.9 Clear channel assessment + +The PHY shall be able to perform a CCA with a threshold of $-80$ dBm. If the RF channel is found to be idle, the PHY may transmit its data. + +In a given deployment, a LBT operation based on CCA shall comply with actual regional RF regulatory requirements, e.g., listening period and sensitivity level. + +#### A.3.1.10 Receiver spurious requirement + +A TRX shall limit its RF emissions when in RX mode. Emissions near the centre frequency may affect the ability of other nearby devices to receive weak signals. + +A receiver shall not emit more than $-70$ dBm within $\pm 1$ MHz from the centre frequency as shown in Figure A.5. The measurement bandwidth shall be 100 kHz. + + + +A graph showing Power on the y-axis and Frequency on the x-axis. A horizontal dashed line at $-70$ dBm / 100 kHz represents the spurious limit. A rectangular box spans from $f_z - 1$ MHz to $f_z + 1$ MHz, with its top edge at the $-70$ dBm / 100 kHz line. The center of the x-axis is labeled 'Center frequency, $f_z$ '. A vertical dashed line with an upward arrow points from the center frequency to the top of the box. The label 'G.9959(15)\_FA.5' is at the bottom right. + +Figure A.5: Receiver spurious limit graph + +Figure A.5 – Receiver spurious limit + +#### A.3.1.11 Receiver blocking + +Blocking is a measure of the capability of the receiver to receive the intended modulated signal without experiencing degradation due to the presence of another unwanted input signal. + +A conforming implementation shall be able to pass a blocking test as described below for all bit rates. + + + +A block diagram showing the test setup. A 'Standard test frame' block and a 'Signal generator unwanted signal' block both connect to a 'Combiner' block. The output of the 'Combiner' block connects to a 'Power meter' block and a 'Receiver' block. The label 'G.9959(15)\_FA.6' is at the bottom right. + +Figure A.6: Receiver blocking test definitions block diagram + +Figure A.6 – Receiver blocking test definitions + +##### Method of measurement: + +- Standard test frames shall be transmitted at the nominal frequency using the modulation specified for the actual data rate. Its power is adjusted down to a power level which is 3 dB higher than the sensitivity level defined in Table A.8; +- The blocking test signal shall be a carrier transmitted at a specific offset frequency as defined in Table A.9. The blocking test signal power shall be increased until the receiver experiences an FER that corresponds to the sensitivity level. + +**Limits:** + +**Table A.9 – Blocking limits** + +| Frequency offset | Limits | +|-------------------------|---------------| +| ±1 MHz | –44 dBm | +| ±2 MHz | –34 dBm | +| ±5 MHz | –27 dBm | +| ±10 MHz | –25 dBm | + +#### **A.3.1.12 Receiver saturation** + +The receiver saturation power level is the maximum power level, in decibels relative to 1 mW, present at the input of the receiver. A receiver shall meet the FER criterion in Table A.7 while receiving at an input level greater than or equal to 0 dBm to sustain "zero" distance between two or more devices. + +#### **A.3.1.13 TX-to-RX turnaround time** + +The TX-to-RX turnaround time shall be measured from the trailing edge of the last transmitted symbol to the leading edge of the first symbol of the received preamble. + +The TX-to-RX turnaround time shall be less than *aPhyTurnaroundTimeTXRX* (see Table A.27). + +Latency estimations shall be calculated on the 99th percentile of all latency measurements. + +#### **A.3.1.14 RX-to-TX turnaround time** + +The RX-to-TX turnaround time shall be measured from the trailing edge of the last received symbol to the leading edge of the first transmitted preamble symbol. + +The RX-to-TX turnaround time shall be more than *aPhyTurnaroundTimeRXTX* (see Table A.27). + +Latency estimations shall be calculated on the 99th percentile of all latency measurements. + +### **A.3.2 PPDU format** + +This clause specifies the format of the PPDU. + +The general PPDU shall be formatted as outlined in Figure A.7. The frame format is depicted in the order in which it is transmitted by the PHY, from left to right, where the leftmost bit is transmitted first in time. Bits within each field are numbered from $k - 1$ (leftmost and most significant) down to 0 (rightmost and least significant), where the length of the field is $k$ bits. Bytes within each multi-byte field are numbered from 1 (leftmost and most significant) up to $n - 1$ (rightmost and least significant), where the length of the field is $n$ bytes. Bits within each byte are numbered from 7 (leftmost and most significant) down to 0 (rightmost and least significant). + +#### A.3.2.1 General PHY frame format + +The PPDU shall be formatted as illustrated in Figure A.7: + + + +| | | | | | +|--------|-------------------|--------------------------|------|------------------------| +| Bytes: | m | 1 | n | 1 | +| | Preamble sequence | Start of frame delimiter | PSDU | End of frame delimiter | +| | SHR | | MPDU | EHR* | +| | PPDU | | | | + +\*R1 only +G.9959(15)\_FA.7 + +**Figure A.7 – PPDU format** + +##### A.3.2.1.1 Preamble field + +The preamble field allows a receiver to obtain symbol synchronization. The preamble field shall be composed of a sequence of bytes containing the binary pattern "01010101". Figure A.8 shows the logical bit waveform of the Manchester encoded preamble for data rate R1. + + + +G.9959(15)\_FA.8 + +Figure A.8: Manchester encoded preamble pattern (R1). The diagram shows a waveform for the bit sequence 0, 1, 0, 1, 0, 1, 0, 1, 1. The first eight bits (01010101) are the preamble, and the ninth bit (1) is the Start of Frame Delimiter (SFD). The waveform for each bit is: 0 is a high-to-low transition, 1 is a low-to-high transition. The SFD bit (1) is shown as a dashed line. + +**Figure A.8 – Manchester encoded preamble pattern (R1)** + +Figure A.9 shows the logical bit waveform of the NRZ encoded preamble pattern for data rates R2 and R3. + + + +G.9959(15)\_FA.9 + +Figure A.9: NRZ encoded preamble pattern (R2, R3). The diagram shows a waveform for the bit sequence 0, 1, 0, 1, 0, 1, 0, 1, 1. The first eight bits (01010101) are the preamble, and the ninth bit (1) is the Start of Frame Delimiter (SFD). The waveform for each bit is: 0 is a high-to-low transition, 1 is a low-to-high transition. The SFD bit (1) is shown as a dashed line. + +**Figure A.9 – NRZ encoded preamble pattern (R2, R3)** + +The preamble length shall comply with Table A.10. The values allow a receiver to scan all channels and obtain synchronization at an arbitrary channel during the duration of the preamble. + +**Table A.10 – Minimum preamble length** + +| Channel configuration | Rate | Minimum preamble length in bytes | | | +|-----------------------|------|----------------------------------|-----------|------| +| | | Singlecast/broadcast | Multicast | Beam | +| 1 | R1 | 10 | 10 | n/a | +| | R2 | 10 | 20 | 20 | +| | R3 | n/a | n/a | n/a | +| 2 | R1 | 10 | 10 | n/a | +| | R2 | 10 | 20 | 20 | +| | R3 | 40 | 40 | n/a | +| 3 | R1 | n/a | n/a | n/a | +| | R2 | n/a | n/a | n/a | +| | R3 | 24 | 24 | 8 | + +##### **A.3.2.1.2 SOF field** + +The SOF delimiter is an 8-bit field terminating the preamble field and the start of the PSDU. The SOF shall be formatted as the logical bit pattern illustrated in Table A.11. + +**Table A.11 – Format of the SOF field** + +| Bit number | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|---|---|---|---|---|---|---|---| +| Value | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | + +##### **A.3.2.1.3 PSDU field** + +The PSDU field has a variable length and carries the data of the PHY frame. + +##### **A.3.2.1.4 EOF delimiter field** + +The EOF delimiter field shall be sent only when transmitting at data rate R1. The field shall carry a sequence of 8 Manchester code violations each denoted E. Each violation, E, shall be a symbol without transition. Refer to Figure A.10. + + + +Timing diagram showing the EOF delimiter pattern for R1. It displays Manchester bit values 1, 0, 0, 1 followed by eight 'E' (violations). The first four bits are labeled 'Data' and the subsequent 'E' symbols are labeled 'End of frame'. The diagram includes a waveform for the first four bits and a flat line for the violations. Source: G.9959(15)\_FA.10 + +**Figure A.10 – EOF delimiter pattern (R1 only)** + +### **A.3.3 PHY service specifications** + +The PHY layer shall provide two services, accessed via two SAPs: the PD, accessed via the PHY data SAP (PD-SAP), and the PHY management service, accessed via the PHY layer management entity SAP (PLME-SAP). The PLME is responsible for maintaining a database of managed objects pertaining to the PHY. This database is referred to as the PHY management information base (MIB). Figure A.11 shows the components and interfaces of the PHY. + + + +Figure A.11 – PHY reference model diagram showing the interaction between MAC layer, PHY layer, and RF-SAP. The MAC layer contains PD-SAP and PLME-SAP. The PHY layer contains PLME and PHY MIB. The RF-SAP is at the bottom. The diagram is labeled G.9959(15)\_FA.11. + +**Figure A.11 – PHY reference model** + +#### **A.3.3.1 PD service** + +The PD-SAP supports the transport of MPDUs between peer MAC entities. Table A.12 lists the primitives supported by the PD-SAP. + +**Table A.12 – PD-SAP primitives** + +| PD-SAP primitive | Request | Confirm | Indication | +|------------------|-----------|-----------|------------| +| PD-DATA | A.3.3.1.1 | A.3.3.1.2 | A.3.3.1.3 | + +##### **A.3.3.1.1 PD-DATA.request** + +The PD-DATA.request primitive requests the transfer of an MPDU (i.e., the PSDU) from the MAC entity to the local PHY entity. + +###### **A.3.3.1.1.1 Semantics of the PD request primitive** + +The semantics of the PD-DATA.request primitive shall be as follows: + +``` +PD-DATA.request ( + psduChannel, + psduRate, + psduLength, + psdu +) +``` + +Table A.13 specifies the parameters for the PD-DATA.request primitive: + +**Table A.13 – PD-DATA.request parameters** + +| Name | Type | Valid range | Description | +|-------------|-------------|-------------------------------------------------------------------------------------------|---------------------------------| +| psduChannel | Enumeration | Channel A, B, C according to the applied RF profile (see Tables A.1 and A.3) | The physical channel to use | +| psduRate | Enumeration | Data rate R1, R2, R3 according to the applied RF profile (see Tables A.1 and A.3) | The data rate to use | +| psduLength | Byte | $\leq aPhyMaxFrameSize_{Rx}$ , where $R_x$ is R1, R2, or R3 depending on actual data rate | The number of bytes to transmit | +| psdu | Byte Array | – | The PSDU to transmit | + +###### A.3.3.1.1.2 When generated + +The PD-DATA.request primitive is generated by the MAC entity and issued to the PHY entity to request the transmission of an MPDU. + +###### A.3.3.1.1.3 Effects on receipt + +The receipt of the PD-DATA.request primitive by the PHY entity shall cause the transmission of the supplied PSDU. Provided the TX is enabled (TX\_ON mode), the PHY shall construct a PPDU, containing the supplied PSDU, and then transmit the PPDU. When the PHY entity has completed the transmission, it shall issue the PD-DATA.confirm primitive with a status of SUCCESS. + +If the PD-DATA.request primitive is received while the receiver is enabled (RX\_ON mode) or if the TRX is disabled (TRX\_OFF mode), the PHY entity shall issue the PD-DATA.confirm primitive with a status of RX\_ON or TRX\_OFF, respectively. + +##### A.3.3.1.2 PD-DATA.confirm + +The PD-DATA.confirm primitive confirms the end of the transmission of an MPDU (i.e., PSDU) from the MAC entity to the physical media. + +###### A.3.3.1.2.1 Semantics of the PD confirm primitive + +The semantics of the PD-DATA.confirm primitive shall be as follows: + +``` +PD-DATA.confirm ( + status +) +``` + +Table A.14 specifies the parameters for the PD-DATA.confirm primitive: + +**Table A.14 – PD-DATA.confirm parameters** + +| Name | Type | Valid range | Description | +|--------|-------------|-------------------------------|---------------------------------------------------------------------------------------------| +| status | Enumeration | SUCCESS,
RX_ON,
TRX_OFF | Transmission was successful
Error: Currently receiving
Error: Transmitter is disabled | + +###### A.3.3.1.2.2 When generated + +The PD-DATA.confirm primitive is generated by the PHY entity and issued to the MAC entity in response to a PD-DATA.request primitive. The PD-DATA.confirm primitive shall return a status of either SUCCESS, indicating that the request to transmit was successful, or an error code of RX\_ON or TRX\_OFF. + +###### A.3.3.1.2.3 Effects on receipt + +The PD-DATA.confirm primitive allows the MAC entity to take proper action when the transmission has been completed. + +##### A.3.3.1.3 PD-DATA.indication + +The PD-DATA.indication primitive indicates the transfer of an MPDU (i.e., PSDU) from the PHY to the local MAC entity. + +###### A.3.3.1.3.1 Semantics of the PD indication primitive + +The semantics of the PD-DATA.indication primitive shall be as follows: + +``` + +PD-DATA.indication ( + psduByte +) + +``` + +Table A.15 specifies the parameters for the PD-DATA.indication primitive. + +**Table A.15 – PD-DATA.indication parameters** + +| Name | Type | Valid range | Description | +|----------|------|-------------|----------------------------------------------------------| +| psduByte | Byte | – | One byte of the PSDU to be transmitted by the PHY entity | + +###### A.3.3.1.3.2 When generated + +The PD-DATA.indication primitive is generated by the PHY entity and issued to the MAC entity to transfer a received PSDU. + +###### A.3.3.1.3.3 Effect on receipt + +On receipt of the PD-DATA.indication primitive, the MAC entity is notified of the arrival of a MPDU data. The MAC layer shall monitor incoming bytes until a complete MPDU has been received. The MAC layer shall use the Length field to determine the length of the MPDU. The MAC layer shall verify the FCS before issuing an MD-DATA.indication to higher layers. + +#### A.3.3.2 PHY management service + +The PLME-SAP allows the transport of management commands between the MLME and the PLME. Table A.16 lists the primitives supported by the PLME-SAP. + +**Table A.16 – PLME-SAP primitives** + +| PLME-SAP primitive | Request | Confirm | Indication | Response | +|--------------------|-----------|-----------|------------|----------| +| PLME-SOF | – | – | A.3.3.2.1 | – | +| PLME-GET-CCA | A.3.3.2.2 | A.3.3.2.3 | – | – | +| PLME-GET | A.3.3.2.4 | A.3.3.2.5 | – | – | +| PLME-SET-TRX-MODE | A.3.3.2.6 | A.3.3.2.7 | – | – | +| PLME-SET | A.3.3.2.8 | A.3.3.2.9 | – | – | + +##### A.3.3.2.1 PLME-SOF.indication + +The PLME-SOF.indication primitive indicates the reception of a SOF delimiter from the PHY to the MAC entity. + +###### A.3.3.2.1.1 Semantics for the service primitive + +The semantics of the PLME-SOF.indication primitive shall be as follows: + +``` + +PLME-SOF.indication ( + psduChannel, + psduRate +) + +``` + +Table A.17 specifies the parameters for the PD-DATA.indication primitive. + +**Table A.17 – PLME-SOF.indication parameters** + +| Name | Type | Valid range | Description | +|-------------|-------------|----------------------|----------------------------------------------| +| psduChannel | Enumeration | Channel A, B, C | The channel from which the PSDU was received | +| psduRate | Enumeration | Data rate R1, R2, R3 | The bit rate of the received PSDU | + +###### **A.3.3.2.1.2 When generated** + +The PLME-SOF.indication primitive is generated by the PLME and issued to the MAC whenever a SOF delimiter is detected by the PHY. + +###### **A.3.3.2.1.3 Effect on receipt** + +The MAC entity is notified of the reception of a SOF delimiter. This information may be used by the MAC entity for preparing frame reception and inhibiting transmissions. + +##### **A.3.3.2.2 PLME-GET-CCA.request** + +The PLME-GET-CCA.request primitive requests a CCA for a specified channel. + +###### **A.3.3.2.2.1 Semantics for the service primitive** + +The semantics of the PLME-GET-CCA.request primitive shall be as follows: + +``` +PLME-GET-CCA.request ( + channel +) +``` + +The table below specifies the parameters for the PLME-GET-CCA.request primitive. + +**Table A-18 – PLME-GET-CCA.request parameters** + +| Name | Type | Valid range | Description | +|---------|-------------|---------------------------------------------------------------------------------|----------------------------------------------------------| +| channel | Enumeration | Channel A, B, or C according to the applied RF profile (see Tables A.1 and A.3) | The physical channel on which the CCA shall be performed | + +###### **A.3.3.2.2.2 When generated** + +The PLME-GET-CCA.request primitive is generated by the MLME and issued to the PLME to request information regarding the specified channel. + +###### **A.3.3.2.2.3 Effect on receipt** + +On receipt of the PLME-GET-CCA.request primitive, the PLME should perform a CCA for the specified channel. When the operation is completed the PLME shall issue a PLME-GET-CCA.confirm advertising the status. + +##### **A.3.3.2.3 PLME-GET-CCA.confirm** + +The PLME-GET-CCA.confirm primitive reports the result of a CCA request. + +###### **A.3.3.2.3.1 Semantics for the service primitive** + +The semantics of the PLME-GET-CCA.confirm primitive shall be as follows: + +``` +PLME-GET-CCA.confirm ( + status +) +``` + +Table A.19 specifies the parameters for the PLME-GET-CCA.confirm primitive. + +**Table A.19 – PLME-GET-CCA.confirm parameters** + +| Name | Type | Valid range | Description | +|--------|-------------|--------------------------------------------|-------------------------------| +| status | Enumeration | CCA_CLEAR,
CCA_NOT_CLEAR,
CCA_RX_OFF | The result of the CCA request | + +###### A.3.3.2.3.2 When generated + +The PLME-GET-CCA.confirm primitive shall be generated by the PLME in response to a PLME-GET-CCA.request primitive. The PLME-GET-CCA.confirm primitive may return a status of CCA\_CLEAR, CCA\_NOT\_CLEAR or RX\_OFF. The CCA\_RX\_OFF status shall be returned if the TRX is not in RX mode (and thus, unable to perform a CCA). + +###### A.3.3.2.3.3 Effect on receipt + +The MLME is notified of the result of the CCA operation. This information may be used by the MAC entity for channel availability evaluation or for deciding whether to transmit now. + +##### A.3.3.2.4 PLME-GET.request + +The PLME-GET.request primitive requests the value of the specified PHY MIB attribute. + +###### A.3.3.2.4.1 Semantics for the service primitive + +The semantics of the PLME-GET.request primitive shall be as follows: + +``` +PLME-GET.request ( + PhyMibAttribute +) +``` + +Table A.20 specifies the parameters for the PLME-GET.request primitive. + +**Table A.20 – PLME-GET.request parameters** + +| Name | Type | Valid range | Description | +|-----------------|-------------|----------------|------------------------------------------------| +| PhyMibAttribute | Enumeration | See Table A.28 | The identifier of the PHY MIB attribute to get | + +###### A.3.3.2.4.2 When generated + +The PLME-GET.request primitive shall be generated by the MLME and issued to the PLME to request information from the PHY MIB. + +###### A.3.3.2.4.3 Effect on receipt + +On receipt of the PLME-GET.request primitive, the PLME should retrieve the value of the specified PHY MIB attribute. + +##### A.3.3.2.5 PLME-GET.confirm + +The PLME-GET.confirm primitive reports the result of an information request from the PHY MIB. + +###### A.3.3.2.5.1 Semantics for the service primitive + +The semantics of the PLME-GET.confirm primitive shall be as follows: + +``` +PLME-GET.confirm ( + status, + PhyMibAttribute, +) +``` + +PhyMibAttributeValue +) + +Table A.21 specifies the parameters for the PLME-GET.confirm primitive. + +**Table A.21 – PLME-GET.confirm parameters** + +| Name | Type | Valid range | Description | +|----------------------|-------------|----------------------------------|----------------------------------------------| +| status | Enumeration | SUCCESS or UNSUPPORTED_ATTRIBUTE | The result of the PHY MIB attribute request | +| PhyMibAttribute | Enumeration | See clause A.3.4.2 | The identifier of the PHY MIB attribute | +| PhyMibAttributeValue | Various | Attribute specific | The value of the specified PHY MIB attribute | + +###### A.3.3.2.5.2 When generated + +The PLME-GET.confirm primitive shall be generated by the PLME in response to a PLME-GET.request primitive. + +If a non-existent PHY MIB attribute is requested, the PLME shall issue the PLME-GET.confirm primitive with a status of UNSUPPORTED\_ATTRIBUTE. + +If the requested PHY MIB attribute is found, the PLME shall issue the PLME-GET.confirm primitive with a status of SUCCESS as well as the MIB attribute identifier and its value. + +###### A.3.3.2.5.3 Effect on receipt + +On receipt of the PLME-GET.confirm primitive, the MLME is notified of the result of the PHY MIB attribute request. If the request was successful, MLME may use the returned MIB attribute value. + +##### A.3.3.2.6 PLME-SET-TRX-MODE.request + +The PLME-SET-TRX-MODE.request primitive requests that the PHY entity changes the operating mode of the TRX. The TRX may be set to one of the modes outlined in Table A.22. + +###### A.3.3.2.6.1 Semantics for the service primitive + +The semantics of the PLME-SET-TRX-MODE.request primitive shall be as follows: + +PLME-SET-TRX-MODE.request ( +mode +) + +Table A.22 specifies the parameters for the PLME-SET-TRX-MODE.request primitive. + +**Table A.22 – PLME-SET-TRX-MODE.request parameters** + +| Name | Type | Valid values | Description | +|------|-------------|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| mode | Enumeration | RX_ON,
TRX_OFF,
FORCE_TRX_OFF, TX_ON | Enable receiver if possible
Disable receiver and transmitter if possible
Force receiver and transmitter off
Enable transmitter if possible | + +###### A.3.3.2.6.2 When generated + +The PLME-SET-TRX-MODE.request primitive may be generated by the MLME and issued to the PLME to change the operational mode of the TRX. + +###### A.3.3.2.6.3 Effect on receipt + +On receipt of the PLME-SET-TRX-MODE.request primitive, the PHY should change the TRX operation mode. + +If the PHY is busy receiving or transmitting, the PHY shall ignore the mode request. + +If this primitive is issued with FORCE\_TRX\_OFF, the PHY shall set the TRX mode to TRX\_OFF irrespective of the current mode. + +##### A.3.3.2.7 PLME-SET-TRX-MODE.confirm + +The PLME-SET-TRX-MODE.confirm primitive shall report the operating mode of the TRX in response to a PLME-SET-TRX-MODE.request. + +If the TRX operation mode is changed, the PHY shall issue the PLME-SET-TRX-MODE.confirm primitive with a status of SUCCESS. + +If the TRX is requested to change to the current operation mode, the PHY shall issue the PLME-SET-TRX-MODE.confirm primitive with a status advertising the current mode, i.e., RX\_ON, TRX\_OFF, or TX\_ON. + +If the TRX is requested to change to the RX\_ON or TRX\_OFF mode and the PHY is busy transmitting, the PHY shall issue the PLME-SET-TRX-MODE.confirm primitive with the status BUSY\_TX. + +If the TRX is requested to change to the TX\_ON or TRX\_OFF mode and the PHY is busy receiving, the PHY shall issue the PLME-SET-TRX-MODE.confirm primitive with the status BUSY\_RX. + +###### A.3.3.2.7.1 Semantics for the service primitive + +The semantics of the PLME-SET-TRX-MODE.confirm primitive shall be as follows: + +PLME-SET-TRX-MODE.confirm ( +status +) + +Table A.23 specifies the parameters for the PLME-SET-TRX-MODE.confirm primitive. + +**Table A.23 – PLME-SET-TRX-MODE.confirm parameters** + +| Name | Type | Valid range | Description | +|--------|-------------|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| status | Enumeration | SUCCESS,
RX_ON,
TRX_OFF,
TX_ON,
BUSY_RX, or
BUSY_TX | Change request was successful
Receiver is enabled
Receiver and transmitter are disabled
Transmitter is enabled
Receiver is enabled and busy
Transmitter is enabled and busy | + +###### A.3.3.2.7.2 When generated + +The PLME-SET-TRX-MODE.confirm primitive is generated by the PLME and issued to the MLME. + +###### A.3.3.2.7.3 Effect on receipt + +The MLME is notified of the operating mode of the TRX. + +The PLME-SET-TRX-MODE.confirm primitive may advertise the status BUSY\_RX or BUSY\_TX. This indicates that the request for a new operation mode was ignored. + +##### **A.3.3.2.8 PLME-SET.request** + +The PLME-SET.request primitive may be issued to request that the specified PHY MIB attribute is set to the specified value. + +###### **A.3.3.2.8.1 Semantics for the service primitive** + +The semantics of the PLME-SET.request primitive shall be as follows: + +PLME-SET.request ( + PhyMibAttribute, + PhyMibAttributeValue +) + +Table A.24 specifies the parameters for the PLME-SET.request primitive. + +**Table A.24 – PLME-SET.request parameters** + +| Name | Type | Valid range | Description | +|----------------------|-------------|--------------------|-----------------------------------------| +| PhyMibAttribute | Enumeration | See clause A.3.4.2 | The identifier of the PHY MIB attribute | +| PhyMibAttributeValue | Various | Attribute specific | The value of the PHY MIB attribute | + +###### **A.3.3.2.8.2 When generated** + +The PLME-SET.request primitive is generated by the MLME and issued to the PLME to set the specified PHY MIB attribute. + +###### **A.3.3.2.8.3 Effect on receipt** + +On receipt of the PLME-SET.request primitive, the PLME should set the specified PHY MIB attribute to the specified value. + +If a non-existent PHY MIB attribute is specified, the PLME shall not change any MIB attribute. + +If the specified value is invalid for the specified PHY MIB attribute, the PLME shall not change the PHY MIB attribute value. + +If the specified PHY MIB attribute is changed, the change should take effect immediately. + +##### **A.3.3.2.9 PLME-SET.confirm** + +The PLME-SET.confirm primitive shall report the result of a request MIB attribute change. + +###### **A.3.3.2.9.1 Semantics for the service primitive** + +The semantics of the PLME-SET.confirm primitive shall be as follows: + +PLME-SET.confirm ( + status, + PhyMibAttribute +) + +Table A.25 specifies the parameters for the PLME-SET.confirm primitive. + +**Table A.25 – PLME-SET.confirm parameters** + +| Name | Type | Valid range | Description | +|-----------------|-------------|---------------------------------------------------------|--------------------------------------------------| +| status | Enumeration | SUCCESS,
UNSUPPORTED_ATTRIBUTE,
INVALID_PARAMETER | The status of the requested MIB attribute change | +| PhyMibAttribute | Enumeration | See clause A.3.4.2 | The identifier of the PHY MIB attribute | + +###### **A.3.3.2.9.2 When generated** + +The PLME-SET.confirm primitive shall be generated by the PLME and issued to the MLME in response to a PLME-SET.request primitive. + +If a non-existent PHY MIB attribute is specified, the PLME shall advertise a status of UNSUPPORTED\_ATTRIBUTE. + +If the specified value is invalid for the specified PHY MIB attribute, the PLME shall advertise a status of INVALID\_PARAMETER. + +If the specified PHY MIB attribute is updated, the PLME shall advertise a status of SUCCESS. + +###### **A.3.3.2.9.3 Effect on receipt** + +The MLME is notified of the result of request PHY MIB attribute change. The MLME should verify that the status parameter advertises the value SUCCESS. Refer to Table A.25. + +#### **A.3.3.3 PHY enumerations description** + +Table A.26 shows PHY enumeration values defined in the PHY specification. + +**Table A.26 – PHY enumerations description** + +| Enumeration | Description | +|-----------------------|-------------------------------------------------------------------------------------------| +| BUSY | The CCA operation detected a busy channel | +| BUSY_RX | The transceiver is receiving and cannot change its mode (unless forced) | +| BUSY_TX | The transceiver is transmitting and cannot change its mode (unless forced) | +| CCA_CLEAR | The CCA operation detected a clear channel | +| FORCE_TRX_OFF | The transceiver shall be disabled, even if it is currently receiving or transmitting data | +| INVALID_PARAMETER | The specified parameter is out of range for the actual MIB attribute | +| CCA_NO_CLEAR | The CCA operation detected a busy channel | +| RX_ON | The receiver is enabled (used for command as well as status) | +| CCA_RX_OFF | The CCA request failed: The receiver is disabled | +| SUCCESS | The operation was successful | +| TRX_OFF | The transceiver is disabled (used for command as well as status) | +| TX_ON | The transmitter is enabled (used for command as well as status) | +| UNSUPPORTED_ATTRIBUTE | The specified MIB attribute is not supported | + +### **A.3.4 PHY constants and MIB attributes** + +This clause specifies the constants and attributes relating to the PHY layer. + +#### A.3.4.1 PHY constants + +The PHY shall comply with the constants defined Table A.27. + +**Table A.27 – PHY constants** + +| Constants | Description | Value | +|--------------------------------|--------------------------------------------------------|----------| +| aPhyMaxFrameSizeR1 | The maximum PSDU size to support at data rate R1 | 64 byte | +| aPhyMaxFrameSizeR2 | The maximum PSDU size to support at data rate R2 | 64 byte | +| aPhyMaxFrameSizeR3 | The maximum PSDU size to support at data rate R3 | 170 byte | +| aPhyTurnaroundTimeTXRX | TX-to-RX maximum turnaround time (see clause A.3.1.13) | 1 ms | +| aPhyTurnaroundTimerRXTX | RX-to-TX minimum turnaround time (see clause A.3.1.14) | 1 ms | + +#### A.3.4.2 PHY MIB attributes + +The PHY management information base (MIB) comprises the attributes required to manage the PHY. Each of these attributes can be read or written using the PLME-GET.request and PLME-SET.request primitives, respectively. The attributes contained in the PHY MIB are presented in Table A.28. + +**Table A.28 – PHY MIB attributes** + +| Attribute | Type | Range | Description | +|----------------------------|-------------|-----------------------------------------------------|-------------------------------| +| phyCurrentTxChannel | Enumeration | A, B, C (Refer to Table A.3) | The TX channel to use | +| phyMapChannelA | Enumeration | Available RF profiles (Refer to Table A.1) | Apply RF profile to channel A | +| phyMapChannelB | Enumeration | Available RF profiles (Refer to Table A.1) | Apply RF profile to channel B | +| phyMapChannelC | Enumeration | Available RF profiles (Refer to Table A.1) | Apply RF profile to channel C | +| phyTransmitPower | Enumeration | Valid output power levels (Refer to clause A.3.1.7) | The transmit power to use | + +## A.4 Medium access (MAC) layer specification + +The MAC layer handles all access to the physical layer and is responsible for the following tasks: + +- Frame ACK; +- Retransmission; +- Providing a reliable link between two peer MAC entities. + +Constants and attributes that are specified and maintained by the MAC layer are written in the text of this clause in italics. Constants have a general prefix of "a", e.g., *aMacMaxFrameRetries*, and are listed in Tables A.47 and A.48. Attributes have a general prefix of "mac", e.g., *macHomeID*, and are listed in Table A.47. + +### A.4.1 MAC layer service specification + +The MAC layer provides an interface between the network layer and the PHY layer. The MLME provides the service interfaces through which layer management functions may be invoked. The MLME is responsible for maintaining a database of managed objects pertaining to the MAC layer. This database is referred to as the MAC layer MAC MIB. Figure A.12 depicts the components and interfaces of the MAC layer. + + + +Figure A.12 – MAC layer reference model diagram. The diagram shows the MAC layer as a sublayer between the Network layer and the PHY layer. The Network layer connects to the MAC sublayer via the MD-SAP and MLME-SAP. The MAC sublayer contains the MD-SAP, PD-SAP, MLME, and PLME-SAP. The MLME is connected to the MAC MIB. The PHY layer connects to the MAC sublayer via the PD-SAP and PLME-SAP. The diagram is labeled G.9959(15)\_FA.12. + +Figure A.12 – MAC layer reference model + +The MAC layer provides two services to the network layer, accessed through two SAPs: + +- The MD service, accessed through the MD-SAP; +- The MAC management service, accessed through the MLME-SAP. + +#### A.4.1.1 MD service + +The MD-SAP supports the transport of NPDU between peer network layer entities. Table A.29 lists the primitives supported by the MD-SAP. The primitives are discussed in the clauses referenced in the table. + +Table A.29 – MD-SAP primitives + +| MD-SAP primitive | Request | Confirm | Indication | +|------------------|-----------|-----------|------------| +| MD-DATA | A.4.1.1.1 | A.4.1.1.2 | A.4.1.1.3 | + +##### A.4.1.1.1 MD-DATA.request + +The MD-DATA.request primitive requests the transfer of an NPDU (i.e., MSDU) from the network layer to the PHY entity. + +###### A.4.1.1.1.1 Semantics of the service primitive + +The semantics of the MD-DATA.request primitive shall be as follows: + +``` +MD-DATA.request ( + SrcHomeID, + SrcNodeID, + DstNodeID, + msduLength, +``` + +msdu, + SequenceNumber, + TxType, + TxOptions, + BeamOption, + RateOption, + ChannelOption, + MulticastOption + ) + +Table A.30 specifies the parameters for the MD-DATA.request primitive: + +**Table A.30 – MD-Data.request parameters** + +| Name | Type | Valid range | Description | +|----------------|-------------|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SrcHomeID | Byte Array | 0x00000000..0xFFFFFFFF | Domain identifier to use | +| SrcNodeID | Byte | 0x00..0xE8 | Source node identifier to use:
0x00: Uninitialized Z-Wave Node ID
0x01 – 0xE8: NodeID
0xE9 – 0xFE: Reserved | +| DstNodeID | Byte | 0x00..0xFF | Destination node identifier to use:
0x00: Reserved
0x01 – 0xE8: NodeID
0xE9 – 0xFE: Reserved
0xFF: Broadcast NodeID | +| msduLength | Byte | $\leq aMacMaxMSDUSizeX$ | Number of bytes to transmit | +| msdu | Byte Array | – | MSDU to transmit | +| SequenceNumber | Byte | – | Unique number of this frame. The same value shall be used for retransmissions | +| TxType | Byte | 0x01..0x03 | Transmission type to use:
0x01 = Singlecast or broadcast transmission
0x02 = Multicast transmission
0x03 = Acknowledged transmission | +| TxOptions | Byte | 0x01, 0x02, 0x04 | Transmission options for this MSDU
The control word is formed as a bit wise OR of one or more of the following values:
0x01 = Routed frame transmission
0x02 = Acknowledged transmission
0x04 = Low power transmission (Note 1) | +| BeamOption | Byte | 0x00, 0x02..0x04 | Battery support options for this MSDU:
0x00: No beam
0x02: Short Continuous beam
0x03: Long Continuous beam
0x04: Fragmented beam | +| ChannelOption | Enumeration | Channel A,B, C (Note 2) | Channel to use | +| RateOption | Enumeration | Data rate R1, R2, R3 according to the applied | Data rate to use | + +**Table A.30 – MD-Data.request parameters** + +| Name | Type | Valid range | Description | +|-----------------|--------------------------|------------------------------------------|--------------------------------------------------------------------------------------| +| | | RF profile (see Tables A.1, A.2 and A.3) | | +| MulticastOption | Byte + Bitmap (30 bytes) | – | If TxType is "Multicast transmission", this bitmap indicates the intended recipients | + +NOTE 1 – Bit 2 (0x04) controls which transmission power level the MAC layer requests from the PHY layer. +NOTE 2 – Channels A, B, and C are preconfigured to RF profiles from the list presented in clause A.3.1.1 via MAC MIB attributes defined in Table A.47. Channel configuration MAC MIB profiles map directly to PHY MIB profiles. + +###### **A.4.1.1.1.2 When generated** + +The MD-DATA.request primitive is generated by a local network layer entity when a data NPDU (i.e., MSDU) is to be transferred to one or more peer network layer entities. + +The TxOptions.LowPower is an option targeting the PHY layer. The option shall make the MAC request the PHY power level defined by the MAC constant aMacTxPhyPowerLevelLow instead of aMacTxPhyPowerLevelNormal. + +###### **A.4.1.1.1.3 Effects on receipt** + +The receipt of the MD-DATA.request primitive by the MAC entity shall cause the transmission of the supplied MSDU. + +The MAC entity builds an MPDU to transmit from the supplied parameters. The TxOptions parameters indicate optional parameters on how the MAC entity transmits the supplied MSDU. + +The MAC entity checks for a CCA (see clause A.4.4.1.1). If the PHY PLME-GET-CCA primitive returns TRUE, the MAC entity enables the TX by issuing the PLME-SET-TRX-MODE.request primitive with a mode of TX\_ON to the PHY. On receipt of the PLME-SET-TRX-MODE.confirm primitive with a status of either SUCCESS or TX\_ON the constructed MPDU is then transmitted by issuing the PD-DATA.request primitive. Finally, on receipt of the PD-DATA.confirm primitive, the MAC entity disables the TX by issuing the PLME-SET-TRX-MODE.request primitive with a mode of RX\_ON to the PHY. + +If the TxOptions parameter specifies that acknowledged transmission is required, the MAC entity shall enable its receiver immediately following the transmission of the MPDU and wait for an ACK for at least *aMacMinAckWaitDuration* symbols. If the MAC entity does not receive an ACK within this time, it shall retransmit the MPDU one or more times as defined by *aMacMaxFrameRetries*. If the MAC entity still does not receive an ACK, it shall discard the MSDU and issue the MD-DATA.confirm primitive with a status of NO\_ACK. + +If the MPDU was successfully transmitted, the MAC entity shall issue the MD-DATA.confirm primitive with a status of SUCCESS. + +If the MPDU could not be transmitted due to a busy channel (see clause A.4.4.1.1), the MAC entity shall issue the MD-DATA.confirm primitive with a status of NO\_CCA. + +If any parameter in the MD-DATA.request primitive is not supported or is out of range, the MAC entity shall issue the MD-DATA.confirm primitive with a status of INVALID\_PARAMETER. + +If the MSDU length is longer than *aMacMaxMSDUSizeX* the MAC entity shall issue the MD-DATA.confirm primitive with a status of FRAME\_TOO\_LONG. + +The MD-Data.request parameters are used to construct the MHR see clause A.4.2. + +##### A.4.1.1.2 MD-DATA.confirm + +The MD-DATA.confirm primitive confirms the transmission of an MSDU. + +###### A.4.1.1.2.1 Semantics of the service primitive + +The semantics of the MD-DATA.confirm primitive shall be as follows: + +``` +MD-DATA.confirm ( + status +) +``` + +Table A.31 specifies the parameters for the MD-DATA.confirm primitive. + +**Table A.31 – MD-Data.confirm parameters** + +| Name | Type | Valid range | Description | +|--------|-------------|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| status | Enumeration | SUCCESS,
NO_ACK,
INVALID_PARAMETER,
NO_CCA,
FRAME_TOO_LONG | Transmission was successful
Transmission was not acknowledged
Transmission aborted; invalid parameter
Transmission aborted; no clear channel
Transmission aborted; frame too long | + +###### A.4.1.1.2.2 When generated + +The MD-DATA.confirm primitive is generated by the MAC entity in response to an MD-DATA.request primitive. The MD-DATA.confirm primitive shall return a status as defined in Table A.31. + +The primitive may be delayed if the MAC has to wait for an ACK. If the frame is transmitted using beaming, the delay may be more than one second. + +###### A.4.1.1.2.3 Effects on receipt + +The MD-DATA.confirm primitive allows higher layers to take proper action whether the transmission was successful or unsuccessful. + +##### A.4.1.1.3 MD-DATA.indication + +The MD-DATA.indication primitive indicates the reception of a data NPDU (i.e., MSDU) from the MAC entity to higher layer entities. + +###### A.4.1.1.3.1 Semantics of the service primitive + +The semantics of the MD-DATA.indication primitive shall be as follows: + +``` +MD-DATA.indication ( + FrmType, + SrcHomeID, + SrcNodeID, + DstNodeID, + msduLength, + msdu, + SequenceNumber, + ChannelOption, + RateOption, + MulticastOption +) +``` + +Table A.32 specifies the parameters for the MD-DATA.indication primitive. + +FrmType indicates if the data delivered to the network layer is a data frame or a beam fragment. + +**Table A.32 – MD-DATA.indication parameters** + +| Name | Type | Valid range | Description | +|-----------------------------------------------------------------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FrmType | Enumeration | 0x01..0xFF | Code indicating the frame type:
0x00: Uninitialized type
0x01: Singlecast frame
0x02: Multicast frame
0x03: ACK frame
0x04..0x07: Not to be used (Note)
0x08: Routed frame
0x09: Beam fragment
0x0A..0xFF: Reserved | +| SrcHomeID | Byte Array | 0x00000000..0xFFFFFFFF
The value 0x00000000 is reserved for un-initialized legacy nodes. HomeID 0x00000000 shall not be used for any domain | The 4-byte domain identifier of the node from which the MSDU was received | +| SrcNodeID | Byte | 0x00..0xFF
The value 0x00 is reserved for un-initialized nodes. | NodeID of the originating node.
0x00: Uninitialized NodeID
0x01..0xE8: NodeID
0xE9..0xFF: Reserved | +| DstNodeID
(Not applicable for multicast frame type) | Byte | 0x00..0xFF | NodeID of the destination node
0x00: Uninitialized NodeID
0x01..0xE8: NodeID
0xE9..0xFE: Reserved
0xFF: Broadcast NodeID | +| msduChannel | Enumeration | Channel A, B, C | The physical channel from which the MSDU was received | +| msduRate | Enumeration | Data rate R1, R2, R3 | The bit rate of the received MSDU | +| msduLength | Byte | $\leq aMacMaxMSDUSizeX$ | The number of received bytes | +| msdu | Byte Array | – | The received MSDU | +| SequenceNumber | Byte | – | The unique number of this frame. Use same value for retransmissions | +| MulticastOption | Byte + Bitmap
(30 bytes) | – | If TxType is "Multicast transmission", this bitmap indicates the intended recipients | +| NOTE – These fields shall not be used due to backwards compatibility. | | | | + +In case of a beam frame, the SrcHomeID field shall be formatted as specified in clause A.4.2.10. + +###### A.4.1.1.3.2 When generated + +The MD-DATA.indication primitive is generated by the MAC entity on receipt of a frame from the PHY layer. If the frame checksum is valid, the frame shall be forwarded to the Z-Wave network layer. + +###### A.4.1.1.3.3 Effects on receipt + +The network layer is notified of the arrival of data. + +Also, beam fragments shall be forwarded to the network layer, which may then forward the beam fragment to higher layers. Higher layers of an FLN node may decide to re-enable sleep mode if the NodeID of a beam fragment is intended for another node. + +##### A.4.1.1.4 Data service message sequence charts + +Figure A.13 illustrates the sequence of messages necessary for a successful data transfer between two nodes. + + + +Figure A.13 – MAC data service message sequence chart. The diagram shows four lifelines: Source network layer, Source MAC layer, Destination MAC layer, and Destination network layer. The sequence of messages is: 1. Source network layer sends MD-DATA.request to Source MAC layer. 2. Source MAC layer sends Data frame to Destination MAC layer. 3. Destination MAC layer sends ACK frame (Optional) back to Source MAC layer. 4. Source MAC layer sends MD-DATA.confirm to Source network layer. 5. Destination MAC layer sends MD-DATA.indication to Destination network layer. The diagram is labeled G.9959(15)\_FA.13. + +Figure A.13 – MAC data service message sequence chart + +#### A.4.1.2 MAC management service + +The MLME-SAP allows the transport of management commands between the next higher layer and the MLME. Table A.33 summarizes the primitives supported by the MLME through the MLME-SAP interface. + +The primitives are discussed in the clauses referenced in the table. + +Table A.33 – MLME-SAP primitives + +| MLME-SAP Primitive | Request | Confirm | Indication | Response | +|--------------------|-----------|-----------|------------|----------| +| MLME-GET | A.4.1.2.1 | A.4.1.2.2 | – | – | +| MLME-SET | A.4.1.2.3 | A.4.1.2.4 | – | – | +| MLME-RESET | A.4.1.2.5 | A.4.1.2.6 | – | – | + +##### A.4.1.2.1 MLME-GET.request + +The MLME-GET.request primitive requests information about a given MAC MIB attribute. + +###### A.4.1.2.1.1 Semantics of the service primitive + +The semantics of the MLME-GET.request primitive shall be as follows: + +``` +MLME-GET.request ( + MacMibAttribute +) +``` + +Table A.33a specifies the parameters for the MLME-GET.request primitive. + +**Table A.33a – MLME-GET.request parameters** + +| Name | Type | Valid range | Description | +|-----------------|---------|----------------|-------------------------------------------------| +| MacMibAttribute | Integer | See Table A.49 | The identifier of the MAC MIB attribute to read | + +###### **A.4.1.2.1.2 When generated** + +The MLME-GET.request primitive is generated by the next higher layer and issued to the MLME to obtain information from the MAC MIB. + +###### **A.4.1.2.1.3 Effects on receipt** + +On receipt of the MLME-GET.request primitive, the MLME attempts to retrieve the requested MAC MIB attribute from its database. If the identifier of the MAC MIB attribute is not found in the database, the MLME shall issue the MLME-GET.confirm primitive with a status of UNSUPPORTED\_ATTRIBUTE. + +If the requested MAC MIB attribute is successfully retrieved, the MLME shall issue the MLME-GET.confirm primitive with a status of SUCCESS and the MAC MIB attribute value. + +##### **A.4.1.2.2 MLME-GET.confirm** + +The MLME-GET.confirm primitive reports the result of a MAC MIB attribute request. + +###### **A.4.1.2.2.1 Semantics of the service primitive** + +The semantics of the MLME-GET.confirm primitive shall be as follows: + +``` + +MLME-GET.confirm ( + status, + MacMibAttribute, + MacMibAttributeValue +) + +``` + +Table A.34 specifies the parameters for the MLME-GET.confirm primitive. + +**Table A.34 – MLME-GET.confirm parameters** + +| Name | Type | Valid range | Description | +|----------------------|-------------|------------------------------------|-------------------------------------------------------------| +| status | Enumeration | SUCCESS or UNSUPPORTED_ATTRIBUTE | The result of the request for MAC MIB attribute information | +| MacMibAttribute | Integer | See Table A.49 | The identifier of the MAC MIB attribute that was read | +| MacMibAttributeValue | Various | Attribute specific, See Table A.49 | The value of the indicated MAC MIB attribute that was read | + +###### **A.4.1.2.2.2 When generated** + +The MLME-GET.confirm primitive is generated by the MLME and issued to the next higher layer in response to an MLME-GET.request primitive. This primitive returns a status of either SUCCESS, indicating that the request to read a MAC MIB attribute was successful, or an error code of UNSUPPORTED\_ATTRIBUTE. + +###### A.4.1.2.2.3 Effects on receipt + +The MLME-GET.confirm primitive reports the result of the MAC MIB attribute request. If the request was successful, the requester may use the returned MIB attribute value. + +##### A.4.1.2.3 MLME-SET.request primitives + +The MLME-SET.request primitive may be used to request that the specified MAC MIB attribute is set to the specified value. + +###### A.4.1.2.3.1 Semantics of the service primitive + +The semantics of the MLME-SET.request primitive shall be as follows: + +``` +MLME-SET.request ( + MacMibAttribute, + MacMibAttributeValue +) +``` + +Table A.35 specifies the parameters for the MLME-SET.request primitive. + +**Table A.35 – MLME-SET.request parameters** + +| Name | Type | Valid range | Description | +|----------------------|---------|------------------------------------|-------------------------------------------------------| +| MacMibAttribute | Integer | See Table A.49 | The identifier of the MAC MIB attribute to write | +| MacMibAttributeValue | Various | Attribute specific, See Table A.49 | The value to write to the indicated MAC MIB attribute | + +###### A.4.1.2.3.2 When generated + +The MLME-SET.request primitive is generated by the next higher layer and issued to the MLME to set the specified MAC MIB attribute. + +###### A.4.1.2.3.3 Effects on receipt + +On receipt of the MLME-SET.request primitive, the MLME should set the specified MAC MIB attribute to the specified value. + +If a non-existent MAC MIB attribute is specified, the MLME shall not change any MIB attribute. + +If the specified value is invalid for the specified MAC MIB attribute, the MLME shall not change the MAC MIB attribute value. + +If the specified MAC MIB attribute is changed, the change should take effect immediately. + +##### A.4.1.2.4 MLME-SET.confirm + +The MLME-SET.confirm primitive shall report the result of the requested MAC MIB attribute change. + +###### A.4.1.2.4.1 Semantics of the service primitive + +The semantics of the MLME-SET.confirm primitive shall be as follows: + +``` +MLME-SET.confirm ( + status, + MacMibAttribute +) +``` + +Table A.36 specifies the parameters for the MLME-SET.confirm primitive. + +**Table A.36 – MLME-SET.confirm parameters** + +| Name | Type | Valid range | Description | +|-----------------|-------------|---------------------------------------------------------|--------------------------------------------------------------------------------------------| +| status | Enumeration | SUCCESS,
UNSUPPORTED_ATTRIBUTE,
INVALID_PARAMETER | Attribute successfully changed
Attribute is not supported
Attribute value is invalid | +| MacMibAttribute | Integer | Table A.49 | The identifier of the MAC MIB attribute that was written. | + +###### **A.4.1.2.4.2 When generated** + +The MLME-SET.confirm primitive shall be generated by the MLME and issued to the next higher layer in response to an MLME-SET.request primitive. + +If a non-existent MAC MIB attribute is specified, the MLME shall advertise a status of UNSUPPORTED\_ATTRIBUTE. + +If the specified value is invalid for the specified MAC MIB attribute, the MLME shall advertise a status of INVALID\_PARAMETER. + +If the specified MAC MIB attribute is updated, the MLME shall advertise a status of SUCCESS. + +###### **A.4.1.2.4.3 Effects on receipt** + +The next higher layer is notified of the result of the MAC MIB attribute change request. The next higher layer should verify that the status parameter advertises the status value SUCCESS. Refer to Table A.36. + +##### **A.4.1.2.5 MLME-RESET.request** + +The MLME-RESET.request primitive allows the next higher layer to request that the MLME performs a reset operation. + +###### **A.4.1.2.5.1 Semantics of the service primitive** + +The semantics of the MLME-RESET.request primitive shall be as follows: + +``` + +MLME-RESET.request ( + SetDefaultMIB +) + +``` + +Table A.37 specifies the parameter for the MLME-RESET.request primitive. + +**Table A.37 – MLME-RESET.request parameters** + +| Name | Type | Valid range | Description | +|---------------|---------|---------------|--------------------------------------------------------------------------------| +| SetDefaultMIB | Boolean | TRUE
FALSE | Reset MAC entity and all MIB attributes
Reset MAC entity state machine only | + +###### **A.4.1.2.5.2 When generated** + +The MLME-RESET.request primitive is generated by the next higher layer and issued to the MLME to request a reset of the MAC entity to its initial conditions. The MLME-RESET.request primitive is issued when a node is excluded from a domain. + +###### **A.4.1.2.5.3 Effects on receipt** + +On receipt of the MLME-RESET.request primitive, the MLME issues the PLME-SET-TRX-STATE.request primitive with a state of TRX\_OFF. On receipt of the PLME-SET-TRX-STATE.confirm primitive, the MAC entity is then set to its initial conditions, clearing all internal + +variables to their default values. If the SetDefaultMIB parameter is set to TRUE, the MAC MIB attributes are set to their default values. + +If the PLME-SET-TRX-STATE.confirm primitive is successful, the MLME shall issue the MLME-RESET.confirm primitive with the status of SUCCESS. Otherwise, the MLME shall issue the MLME-RESET.confirm primitive with the status of DISABLE\_TRX\_FAILURE. + +##### A.4.1.2.6 MLME-RESET.confirm + +The MLME-RESET.confirm primitive reports the results of the reset operation. + +###### A.4.1.2.6.1 Semantics of the service primitive + +The semantics of the MLME-RESET.confirm primitive shall be as follows: + +``` +MLME-RESET.confirm ( + status +) +``` + +Table A.38 specifies the parameter for the MLME-RESET.confirm primitive. + +**Table A.38 – MLME-RESET.confirm parameters** + +| Name | Type | Valid range | Description | +|--------|-------------|--------------------------------|--------------------------------------------------------------------| +| status | Enumeration | SUCCESS
DISABLE_TRX_FAILURE | MAC entity successfully reset
MAC entity reset operation failed | + +###### A.4.1.2.6.2 When generated + +The MLME-RESET.confirm primitive is generated by the MLME and issued to the next higher layer in response to an MLME-RESET.request primitive and following the receipt of the PLME-SET-TRX-STATE.confirm primitive. + +###### A.4.1.2.6.3 Effects on receipt + +On receipt of the MLME-RESET.confirm primitive, the next higher layer is notified of the request to reset the MAC entity. This primitive shall return a status as defined in Table A.38. + +#### A.4.1.3 MAC enumeration description + +This clause explains the meaning of the enumerations used in the primitives defined in the MAC entity specification. Table A.39 shows a description of the MAC enumeration values. + +**Table A.39 – MAC enumerations description** + +| Enumeration | Description | +|-----------------------|-----------------------------------------------------------------------------------------------| +| SUCCESS | The requested operation was completed successfully | +| DISABLE_TRX_FAILURE | The attempt to disable the TRX has failed | +| FRAME_TOO_LONG | The frame has a length that is greater than aMacMaxMSDUSizeX | +| INVALID_PARAMETER | A parameter in the primitive is out of the valid range | +| NO_ACK | No ACK was received after aMacMaxFrameRetries | +| NO_CCA | No clear channel access was possible after a period of .macCCARetryDuration | +| UNSUPPORTED_ATTRIBUTE | A SET/GET request was issued with the identifier of a MAC MIB attribute that is not supported | + +### A.4.2 MPDU formats + +This clause specifies the format of the MPDU. Each MPDU consists of the following basic components: + +1. An MHR, which comprises address, frame control, and length information; +2. A MAC data payload, of variable length, which contains information specific to the frame type; +3. An MFR, which contains a FCS. + +The MPDU is defined as a sequence of fields. All MPDU formats in this clause are depicted in the order in which they are transmitted by the PHY, from left to right, where the leftmost bit is transmitted first in time. Bits within each field are numbered from $k - 1$ (leftmost and most significant) down to 0 (rightmost and least significant), where the length of the field is $k$ bits. Bytes within each multi-byte field are numbered from 1 (leftmost and most significant) up to $n - 1$ (rightmost and least significant), where the length of the field is $n$ bytes. Bits within each byte are numbered from 7 (leftmost and most significant) down to 0 (rightmost and least significant). + +The general MPDU format comprises the fields MHR, data payload, and MFR. The general MPDU shall be formatted as illustrated in Figure A.14. + +The MPDU formats for channel configurations 1, 2, and channel configuration 3 are explained in the following clauses. + +Singlecast MPDUs shall use the formats outlined in Figures A.14 and A.15. + + + +| | | | | | | | | +|-----------|--------|----------------|---------------|--------|---------------------|--------------|--------| +| Bytes: | 4 | 1 | 2 | 1 | n | m | 1 or 2 | +| MAC layer | HomeID | Source node ID | Frame control | Length | Destination node ID | Data payload | FCS | +| | MHR | | | | MSDU | | MFR | +| | MPDU | | | | | | | + +G.9959(15)\_FA.14 + +Figure A.14 – General MPDU format (Channel configurations 1, 2 only). This diagram shows the byte structure of an MPDU. The fields are: HomeID (4 bytes), Source node ID (1 byte), Frame control (2 bytes), Length (1 byte), Destination node ID (n bytes), Data payload (m bytes), and FCS (1 or 2 bytes). The first four fields (HomeID through Length) constitute the MAC Header (MHR). The next field (Destination node ID through Data payload) constitutes the MAC Service Data Unit (MSDU). The final field (FCS) constitutes the MAC Footer (MFR). The entire sequence is labeled as the MPDU. + +**Figure A.14 – General MPDU format (Channel configurations 1, 2 only)** + + + +| | | | | | | | | | +|-----------|--------|----------------|---------------|--------|-----------------|---------------------|--------------|-----| +| Bytes: | 4 | 1 | 2 | 1 | 1 | n | m | 2 | +| MAC layer | HomeID | Source node ID | Frame control | Length | Sequence number | Destination node ID | Data payload | FCS | +| | MHR | | | | | MSDU | | MFR | +| | MPDU | | | | | | | | + +G.9959(15)\_FA.15 + +Figure A.15 – General MPDU format (Channel configuration 3 only). This diagram shows the byte structure of an MPDU for channel configuration 3. The fields are: HomeID (4 bytes), Source node ID (1 byte), Frame control (2 bytes), Length (1 byte), Sequence number (1 byte), Destination node ID (n bytes), Data payload (m bytes), and FCS (2 bytes). The first five fields (HomeID through Sequence number) constitute the MAC Header (MHR). The next field (Destination node ID through Data payload) constitutes the MAC Service Data Unit (MSDU). The final field (FCS) constitutes the MAC Footer (MFR). The entire sequence is labeled as the MPDU. + +**Figure A.15 – General MPDU format (Channel configuration 3 only)** + +The multicast MPDU shall use the formats outlined in Figures A.16 and A.17. + + + +| | | | | | | | | | +|-----------|--------|----------------|---------------|--------|-------------------|--------------------|--------------|--------| +| Bytes: | 4 | 1 | 2 | 1 | 1 | 29 | m | 1 or 2 | +| MAC layer | HomeID | Source node ID | Frame control | Length | Multicast control | Multicast bit mask | Data payload | FCS | +| | MHR | | | | | MSDU | | MFR | +| | MPDU | | | | | | | | + +G.9959(15)\_FA.16 + +Figure A.16 – Multicast MPDU format (Channel configurations 1, 2 only). This diagram shows the byte structure of a multicast MPDU. The fields are: HomeID (4 bytes), Source node ID (1 byte), Frame control (2 bytes), Length (1 byte), Multicast control (1 byte), Multicast bit mask (29 bits), Data payload (m bytes), and FCS (1 or 2 bytes). The first five fields (HomeID through Multicast control) constitute the MAC Header (MHR). The next field (Multicast bit mask through Data payload) constitutes the MAC Service Data Unit (MSDU). The final field (FCS) constitutes the MAC Footer (MFR). The entire sequence is labeled as the MPDU. + +**Figure A.16 – Multicast MPDU format (Channel configurations 1, 2 only)** + + + +Figure A.17 – Multicast MPDU format (Channel configuration 3). This diagram shows the structure of a MAC Protocol Data Unit (MPDU) for multicast. It consists of several fields: HomeID (4 bytes), Source node ID (1 byte), Frame control (2 bytes), Length (1 byte), Sequence number (1 byte), Multicast control (1 byte), Multicast bit mask (29 bytes), Data payload (m bytes), and FCS (2 bytes). The first six fields (HomeID through Multicast control) are grouped as the MAC Header (MHR). The next six fields (Multicast bit mask through Data payload) are grouped as the MAC Service Data Unit (MSDU). The entire MPDU (MHR + MSDU + FCS) is shown with a double-headed arrow at the bottom. A label 'G.9959(15)\_FA.17' is in the bottom right corner. + +**Figure A.17 – Multicast MPDU format (Channel configuration 3)** + +Refer to clause A.4.2.5.1 for details on transmission and processing of multicast frames. + +#### A.4.2.1 HomeID + +The HomeID identifier field is 4 bytes in length and specifies the unique domain identifier. All nodes in a domain shall have the same HomeID. + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|----------------|---|---|---|---|---|---|---| +| 0 | HomeID (0) MSB | | | | | | | | +| 1 | HomeID (1) | | | | | | | | +| 2 | HomeID (2) | | | | | | | | +| 3 | HomeID (3) LSB | | | | | | | | + +G.9959(15)\_FA.18 + +**Figure A.18 – Format of a HomeID field** + +The MAC layer shall support configuration of a promiscuous mode, forwarding all MPDUs to higher layers. Refer to clause A.4.4.1.3. + +#### A.4.2.2 Source NodeID + +The source NodeID is 8 bits in length and shall be a unique identifier of a node in a given domain. Together with the HomeID, the source NodeID identifies the node that originated the frame. + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|---------------|---|---|---|---|---|---|---| +| 4 | Source NodeID | | | | | | | | + +G.9959(15)\_FA.19 + +**Figure A.19 – Source NodeID field** + +The source NodeID shall comply with Table A.40. + +**Table A.40 – Source NodeID values** + +| NodeID | Usage | +|------------|----------------------| +| 0x00 | Uninitialized NodeID | +| 0x01..0xE8 | NodeID | +| 0xE9..0xFE | Reserved | + +#### A.4.2.3 Frame control + +The Frame Control field is 16 bits in length and contains information defining the frame type and other control flags. The frame control field shall be formatted as illustrated in Figures A.20 and A.21. + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|----------|---------------|-----------|----------------|-----------------|---|---|---| +| 5 | Routed | ACK Req. | Low power | Speed modified | Header type | | | | +| 6 | Reserved | Beaming Info. | | Reserved | Sequence number | | | | + +G.9959(15)\_FA.20 + +**Figure A.20 –Frame Control field (Channel configurations 1, 2 only)** + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|----------|---------------|----------|----------|-------------|---|---|---| +| 5 | ACK Req. | Low power | Reserved | | Header type | | | | +| 6 | Reserved | Beaming Info. | | Reserved | | | | | + +G.9959(15)\_FA.21 + +**Figure A.21 – Format of a frame control field (Channel configuration 3)** + +##### A.4.2.3.1 Routed subfield (Channel configurations 1, 2 only) + +The Routed subfield is 1 bit in length and shall be set to 0 when the frame is not routed and set to 1 when the frame is routed. The use of this field is out of scope of this Recommendation. + +##### A.4.2.3.2 ACK Req subfield + +The ACK Req subfield is 1 bit in length and set to 1 when the source node wants the destination node to acknowledge the frame, and the bit is set to 0 when no ACK is needed. + +A receiving node shall return an ACK MPDU in response to the ACK request. + +##### A.4.2.3.3 Low power subfield + +The Low Power subfield is 1 bit in length and is set by the source node. The bit informs a destination node that the actual transmission was using low power. + +A receiving node shall return an ACK MPDU in low power in response to the low power bit. + +##### A.4.2.3.4 Speed modified subfield (Channel configurations 1, 2 only) + +The Speed modified subfield is 1 bit in length. It shall be set to 1 if an MPDU is sent at a lower speed than supported by the source and destination. The field shall not be used for routed and multicast MPDUs. The field shall be set to 0 if the MPDU is sent at the highest speed supported by the source and destination. + +##### A.4.2.3.5 Header type subfield + +The header type subfield defines the frame header type. + +**Table A.41 – Header type** + +| Header type value | Description | +|-------------------|-----------------------------------------------| +| 0x1 | Singlecast MPDU | +| 0x2 | Multicast MPDU | +| 0x3 | ACK MPDU | +| 0x4..0x7 | Not to be used (Note) | +| 0x8 | Routed MPDU
(Channel configuration 3 only) | +| 0x9..0xB | Not to be used (Note) | +| 0xC..0xF | Reserved | + +NOTE – These values shall not be transmitted due to backward compatibility. Received frames shall be forwarded to higher layers. + +A broadcast MPDU is a singlecast MPDU (header type 0x1) carrying a destination NodeID = 0xFF, see clause A.4.2.6. + +A receiving node shall forward routed MPDUs to higher layers. The transmission of routed MPDUs is out of scope of this Recommendation. + +##### A.4.2.3.6 Beaming Information + +The Beaming Information subfield shall advertise the capability of a sending FL node to be awakened by a beam if it is asleep. The Beaming Information subfield shall be interpreted in combination with the actual channel configuration. + +**Table A.42 – Beaming information, channel configuration 1, 2** + +| Channel configuration | Beam information value | Description | +|-----------------------|----------------------------|-----------------------| +| 1,2 | Frame control[6..5] = "00" | No beam | +| 1,2 | Frame control[6..5] = "01" | Short continuous beam | +| 1,2 | Frame control[6..5] = "10" | Long continuous beam | +| 1,2 | Frame control[6..5] = "11" | Reserved | + +**Table A.43 – Beaming information, channel configuration 3** + +| Channel configuration | Beam information value | Description | +|-----------------------|-----------------------------|-----------------| +| 3 | Frame control[6..4] = "000" | Reserved | +| 3 | Frame control[6..4] = "001" | Reserved | +| 3 | Frame control[6..4] = "010" | Reserved | +| 3 | Frame control[6..4] = "011" | Reserved | +| 3 | Frame control[6..4] = "100" | Fragmented beam | +| 3 | Frame control[6..4] = "101" | Reserved | +| 3 | Frame control[6..4] = "110" | Reserved | +| 3 | Frame control[6..4] = "111" | Reserved | + +##### A.4.2.3.7 Sequence Number (Channel configurations 1, 2 only) + +The Sequence Number is a 4-bit sub-field of the frame control field. The Sequence Number is provided by higher layers when transmitting. The MAC layer of a transmitting node shall forward the sequence number value transparently to the PHY. The MAC layer of a receiving node shall forward the sequence number value transparently to higher layers. + +The MAC layer shall use the same sequence number for the initial transmission and for all retransmissions of a given MPDU. The transmitted sequence number shall be in the range 0x1..0xf. The value 0xf shall be followed by the value 0x1. + +A receiving node shall accept any sequence number value in the range 0x0..0xf. The receiving node shall return the same value in an ACK MPDU if ACK is requested. A transmitting node shall validate the received sequence number in an ACK MPDU. In order to support legacy implementations, a transmitting node which receives an ACK MPDU shall accept the sequence number value zero irrespective of the sequence number transmitted. + +#### A.4.2.4 Length + +The Length field is 1 byte in length and shall indicate the length of the MPDU in bytes. + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|--------|---|---|---|---|---|---|---| +| 7 | Length | | | | | | | | + +G.9959(15)\_FA.22 + +Figure A.22 – Length field + +The length is limited to *aMacMaxMSDUSizeX*. The actual values can be found in Tables A.47 and A.48. A receiving node shall not read more bytes than the maximum length allowed for the actual data rate. + +#### A.4.2.5 Sequence number (Channel configuration 3 only) + +The sequence number is an 8-bit field of the MPDU Header (MHR). The MAC layer of a transmitting node shall forward the sequence number value transparently to the PHY. The MAC layer of a receiving node shall forward sequence number value transparently to higher layers. + +The MAC layer shall use the same sequence number for the initial transmission and for all retransmissions of a given MPDU. The transmitted sequence number shall be in the range 0x00..0xff. The value 0xff shall be followed by the value 0x00. + +A receiving node shall accept any sequence number value in the range 0x00..0xff. The receiving node shall return the same value in an ACK MPDU if ACK is requested. A transmitting node shall validate the received sequence number in an ACK MPDU. + +#### A.4.2.6 Destination NodeID + +The destination NodeID shall specify a destination node in the same domain identified by the HomeID. + +The destination NodeID value shall comply with Table A.44: + +**Table A.44 – Destination NodeID** + +| NodeID | Node type | +|------------|----------------------| +| 0x00 | Uninitialized NodeID | +| 0x01..0xE8 | NodeID | +| 0xE9..0xFE | Reserved | +| 0xFF | Broadcast NodeID | + +The destination NodeID value 0xFF may be used for broadcasting an MPDU to all nodes within direct range. The MAC layer of a receiving node shall always forward a broadcast MPDU to higher layers. + +The MAC layer shall support the configuration of a promiscuous receiver mode, forwarding all MPDUs to higher layers irrespective of the actual destination NodeID. + +##### A.4.2.6.1 Multicast destination fields + +A multicast MPDU shall carry a Multicast Control field and a multi-byte multicast bit mask as shown in Figure A.23. + +| Byte \ Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|------------|----------------|---|---|----------------------|---|---|---|---| +| 8 | Address Offset | | | Number of mask bytes | | | | | +| 9 | | | | Mask byte 0 | | | | | +| 10 | | | | Mask byte 1 | | | | | +| 11 | | | | Mask byte 2 | | | | | +| ... | | | | ..... | | | | | +| 37 | | | | Mask byte 28 | | | | | + +G.9959(15)\_FA.23 + +**Figure A.23 – Multicast destination address format** + +A receiving node shall not acknowledge a multicast MPDU. A sending node shall set the ACK Req bit of a multicast MPDU to zero. Likewise, a sending node shall set the Address Offset field to zero and the number of mask bytes field shall be set to 29. + +A receiving node shall support the values of the Address Offset field outlined in Table A.45. + +The address offset field is a 3-bit field. The encoding of the field is outlined in Table A.45. + +**Table A.45 – Multicast address offset encoding** + +| Address offset value | Bit address offset | +|----------------------|--------------------| +| 0 | 0 | +| 1 | 32 | +| 2 | 64 | +| 3 | 96 | +| 4 | 128 | +| 5 | 160 | +| 6 | 192 | +| 7 | 224 | + +Each bit of a mask byte represents a node. Mask byte 0 represents the NodeIDs 1 to 8. + +As an example a mask byte 0 value of 0xC5 (in binary: 11000101) covers nodeIDs 1, 3, 7, and 8 while a mask byte 1 value of 0xC5 (in binary: 11000101) covers nodeIDs 9, 11, 15, and 16. + +The destination NodeID can be calculated using the following formula. + +$$\text{Destination NodeID} = \text{bit address offset} + \text{mask byte number} \times 8 + \text{mask bit number} + 1$$ + +#### **A.4.2.7 Data payload** + +The data payload field has a variable length. An ACK MPDU may carry zero or more data payload bytes. A receiving node may derive the length of the data payload field from the MPDU Length field. + +#### **A.4.2.8 FCS** + +An 8-bit non-correcting FCS shall be used for validating the MPDU integrity for data rates R1 and R2. The FCS shall be calculated from the HomeID field to the Data Payload field, both included, as shown in Figure A.24. + + + +The diagram shows an MPDU structure with the following fields: HomeID, Source node ID, Frame control, Length, Destination node ID, Data payload, and FCS. A bracket labeled 'FCS coverage' spans from the start of the HomeID field to the start of the FCS field, indicating the data included in the FCS calculation. The source G.9959(15)\_FA.24 is noted at the bottom right. + +Diagram of MPDU structure showing fields: HomeID, Source node ID, Frame control, Length, Destination node ID, Data payload, and FCS. A bracket labeled 'FCS coverage' spans from the start of HomeID to the start of FCS. + +**Figure A.24 – FCS coverage** + + + +The diagram shows the FCS field structure. It is an 8-bit byte divided into bits 7 through 0. The label 'Frame check sequence' is placed across the bits. The source G.9959(15)\_FA.25 is noted at the bottom right. + +Diagram of the FCS field structure showing 8 bits (0-7) and the label 'Frame check sequence'. + +**Figure A.25 – FCS field** + +The FCS shall be calculated as an odd (XOR'ed) checksum as shown in the following algorithm. + +``` + +BYTE GenerateCheckSum(BYTE *Data, BYTE Length) +{ + BYTE CheckSum = 0xFF; + for (; Length > 0; Length--) + { + CheckSum ^= *Data++; + } + return CheckSum; +} + +``` + +#### A.4.2.9 CRC + +A 16-bit non-correcting CRC shall be used for validating the MPDU integrity for data rate R3. + + + +| | | | | | | | +|--------|----------------|---------------|--------|---------------------|--------------|-----| +| HomeID | Source node ID | Frame control | Length | Destination node ID | Data payload | CRC | +|--------|----------------|---------------|--------|---------------------|--------------|-----| + +| CRC | + +G.9959(15)\_F8-17 + +**Figure A.26 – CRC coverage** + +The CRC-16 generator polynomial shall be: + +$$P(x) = x^{16} + x^{12} + x^5 + 1, \text{ also known as CRC-CCITT.}$$ + +The CRC-16 shall be calculated over the whole frame, except for the preamble, SOF, and the CRC-16 fields. + +The CRC-16 generator shall be initialized to 1D0Fh before applying the first frame byte of a frame. Additional bits shall not be appended the frame data. + +#### A.4.2.10 Beam frame format + +Beam frames may be used to awaken battery powered nodes operating in FL mode. Beam frames are used for several beam types. Beam frames are transmitted back-to-back to ensure an FL node can detect a beam within a very short time window before returning to sleep. + +Each beam frame carries a preamble sequence and an SOF field, just like the start of any other PHY PDU. The SOF is followed by two or three bytes, replacing the HomeID field found in a general MPDU. A receiving node may distinguish a general MPDU from a beam frame by inspecting the MS byte of the HomeID. If this byte carries a beam tag (refer to Table A.46) this is a beam frame and the following one or two bytes carry beaming relevant information. + + + +(Start of) +MPDU header + +| | | | | | | +|--------|-------------------|----------------|--------------------------------------|--------|-------------| +| Bytes: | 8/20 | 1 | 1 | 1 | 1 | +| | Preamble sequence | Start of frame | Beam Tag = 0x55 | NodeID | HomeID hash | +| | PPDU header | | (Optional)
HomeID of general MPDU | | | + +G.9959(15)\_FA.27 + +**Figure A.27 – Beam frame (Tag = 0x55)** + +The preamble sequence length depends on the actual RF profile used. A node shall listen long enough to detect a beam frame during worst case conditions around the SOF, beam tag, and beam information. In a worst-case situation, a node in FL mode starts listening just when it is too late to achieve lock to the preamble sequence. In this case, the node has to wait until another preamble sequence starts. Only after achieving lock to the preamble, the SOF and beam tag fields may be correctly decoded. + +Each beam frame shall carry the beam tag and NodeID fields. The NodeID field should be followed by the optional HomeID Hash field. + +**Table A.46 – Beam frame fields** + +| Field name | Value | Description | +|---------------------------|---------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Beam tag | 0x55 | HomeID MSB reserved for beam frame transmission
HomeIDs in the range 0x55000000..0x55FFFFFF shall not be assigned to any domain
The beam tag value 0x55 shall advertise the presence of a NodeID field and an optional HomeID Hash field | +| | 0x54
( reserved ) | HomeID MSB reserved for beam frame transmission
HomeIDs in the range 0x54000000..0x54FFFFFF shall not be assigned to any domain
The beam tag value 0x54 shall be reserved for future use | +| NodeID | 1..232, 255 | Destination NodeID. If the value is 255 or it matches the NodeID of an FL node, the node shall also inspect the HomeID Hash field. If no match is found, the FL node should return to sleep. | +| HomeID Hash
(optional) | Hashed 8-bit version of the HomeID
Ignore if 0x0A, 0x4A or 0x55. | Hash value for preventing NodeID collisions in dense network environments with overlapping domains.
Refer to text following this table. | + +It is recommended that any node implements support for the HomeID Hash field presented in Figure A.27 and Table A.46. + +The HomeID hash value shall be calculated as shown in the following algorithm. + +``` + +BYTE GenerateHomeIdHash(BYTE *HomeId) +{ + BYTE HomeIdHash = 0xFF; + for (Length = 4; Length > 0; Length--) + { + HomeIdHash ^= *HomeId++; + } + switch (HomeIdHash) + { + Case 0x0A: + Case 0x4A: + Case 0x55: + HomeIdHash++; + } + return HomeIdHash; +} + +``` + +A sending node should include a HomeID Hash field in the beam frame (Tag 0x55) to assist FL nodes in filtering out beam frames belonging to other domains. + +A FL node receiving one of the HomeID hash values 0x0A, 0x4A, or 0x55 shall accept the value as a potential match to the actual HomeID and therefore it shall stay awake to receive the MPDU that follows if there is a match for the NodeID. Likewise, an FL node shall stay awake to receive the MPDU that follows if it detects a match to the hashed version of its own HomeID and if there is also a match for the actual NodeID. In case of no match for HomeID hash and/or NodeID, the node may return to sleep immediately. + +#### A.4.2.11 Fragmented beam format + +A beam fragment shall comprise a number of beam frames. The beam fragment duration shall be in the range 110-115 ms. Beam frames shall be sent back-to-back to ensure that the beam fragment can be detected by a node waking up at any moment during the duration of the beam fragment. + + + +The diagram illustrates the internal structure of a beam fragment. It shows four individual 'Beam frame' blocks at the beginning, followed by an ellipsis '...', and a final 'Beam fragment' block. A horizontal dashed line spans the entire duration of these elements, labeled '110 ms'. Below this timeline, a solid grey bar is labeled 'Beam fragment'. The text 'G.9959(15)\_FA.28' is located in the bottom right corner. + +Diagram of a beam fragment showing four beam frames followed by an ellipsis and a final beam fragment, all within a 110 ms duration. + +Figure A.28 – Format of the beam fragment + +A fragmented beam shall comprise a number of beam fragments. The next beam fragment shall begin in the range 190-200 ms measured from the beginning of the previous beam fragment. Fragmented beams shall be sent at data rate R3. A receiver shall be able to monitor multiple channels for beam frames. + + + +The diagram shows the sequence of beam fragments within a fragmented beam. It displays three 'Beam fragment' blocks. Above the first fragment is a duration of '110.. 115 ms'. Above the second fragment is also '110.. 115 ms'. Above the third fragment is '110.. 115 ms'. A horizontal dashed line indicates a gap of '190.. 200 ms' between the start of the first and second fragments. Another horizontal dashed line spans the total duration of the three fragments and gaps, labeled '3000 ms'. Below this timeline, a solid grey bar is labeled 'Fragmented beam'. The text 'G.9959(15)\_FA.29' is located in the bottom right corner. + +Diagram of a fragmented beam showing three beam fragments with a 190-200 ms gap between them, spanning a total of 3000 ms. + +Figure A.29 – Format of the fragmented beam + +Proper TX scheduling allows a sending node to reach sleeping nodes that use a range of wakeup intervals 100 ms, 150 ms, 250 ms, 500 ms, 700 ms, 900 ms. The chosen wakeup interval should be a trade-off between battery lifetime and response time. + +A fragmented beam may address any NodeID and also the broadcast NodeID 0xFF. A full fragmented beam shall span 3000 ms. A singlecast frame shall follow the fragmented beam. A receiving node may interrupt the transmission of a fragmented beam by acknowledging a singlecast beam fragment. A receiving node shall not acknowledge a broadcast beam fragment. A receiving FL node detecting a positive match for the HomeID Hash field of the beam frame may return the ACK MPDU immediately. A receiving FL node not detecting a positive match for the HomeID Hash field shall apply a random delay of 0..50 ms to the ACK MPDU to prevent collisions between FL nodes having the same NodeID in different domains. + +In response to an ACK MPDU, the originating node shall transmit the MPDU to the receiving node if the Src HomeID of the ACK MPDU matches the HomeID of the beaming node. If the HomeID or NodeID does not match, the originating node shall ignore the ACK MPDU. + +A.4.2.12 (intentionally left blank) + +#### A.4.2.13 Continuous beam format + +A continuous beam is a series of beam frames spanning a fixed period of time. The beam frames shall be sent back-to-back to prevent other TXs from interrupting the continuous beam. The continuous beam shall be sent at data rate R2. + +A continuous beam may address any NodeID, and also the broadcast NodeID (0xFF). + +There are two types of continuous beams: long and short. A long continuous beam may last for a maximum of 1160 ms, and a short one may last for a maximum of 300 ms. The recommended duration is 1100 ms for a long continuous beam and 275 ms for a short continuous beam. A continuous beam shall always be followed by a singlecast frame. + +#### A.4.2.14 Beam formats on channel configurations 1 and 2 + +FL nodes operating in channel configuration 1 or 2 shall be able to receive and transmit the continuous beam format at data rate R2. + +#### A.4.2.15 Beam formats on channel configuration 3 + +FL nodes operating in channel configuration 3 shall be able to receive and transmit the fragmented beam format at data rate 3. + +### A.4.3 MAC constants and MIB attributes + +This clause specifies the constants and attributes used by the MAC. + +#### A.4.3.1 MAC constants + +The constants used by the MAC layer are presented in Table A.47. These constants are hardware dependent and cannot be changed during operation. + +**Table A.47 – MAC constants in general** + +| Constants | Description | Value | +|----------------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------------| +| aMacMaxMSDUSizeR1 | The maximum singlecast/broadcast MSDU size for data rate R1 | 54 bytes | +| aMacMaxMSDUSizeMultiR1 | The maximum multicast MSDU size for data rate R1 | 25 bytes | +| aMacMaxMSDUSizeR2 | The maximum singlecast/broadcast MSDU size for data rate R2 | 54 bytes | +| aMacMaxMSDUSizeMultiR2 | The maximum multicast MSDU size for data rate R2 | 25 bytes | +| aMacMaxMSDUSizeR3 | The maximum singlecast/broadcast MSDU size for data rate R3 | 158 bytes | +| aMacMaxMSDUSizeMultiR3 | The maximum multicast MSDU size for data rate R3 | 129 bytes | +| aMacMinAckWaitDuration | The minimum ACK wait duration | $aPhyTurnaroundTimeRxTx + (aMacTransferAckTimeTX * (1/\text{data rate}))$ | +| aMacMaxFrameRetries | The number of retries after a transmission failure | 2 | +| aMacMinCCARetryDuration | The minimum duration of clear channel access assessment | 1100 ms | +| aMacTxPhyPowerLevelLow | The value used for phyTransmitPower to transmit at low power | Implementation dependent | +| aMacTxPhyPowerLevelNormal | The value used for phyTransmitPower to transmit at normal power | Implementation dependent | + +The term *aMacMaxMSDUSizeX* is used in text that applies to all data rates (*aMacMaxMSDUSizeR1*, *aMacMaxMSDUSizeR2*, *aMacMaxMSDUSizeR3*, *aMacMaxMSDUSizeMultiR1*, *aMacMaxMSDUSizeMultiR2*, *aMacMaxMSDUSizeMultiR3*). + +Retransmitted frames may cause prolonged transmission times as the retransmission uses longer preambles in certain transmission modes. + +Table A.48 outlines the constant values to use for message transfer at data rates R1, R2, R3. + +**Table A.48 – MAC constants for MPDU transfer** + +| Constants | Description | R1 | R2 | R3 | | +|--------------------------------------|---------------------------------------------------------------------------|----------|----------|------------------|---------------| +| | | | | Channel Cfg 1, 2 | Channel Cfg 3 | +| aMacTransferAckTimeTX (ch) | The number of symbols of an ACK MPDU, including preamble | 168 bits | 248 bits | 416 bits | 296 bits | +| aMacTypicalFrameLengthTX (ch) | The number of symbols of a singlecast MPDU with a data payload of 4 bytes | 200 bits | 280 bits | 448 bits | 328 bits | +| aMacMinRetransmitDelay | Random backoff shall be higher than this value | 10 ms | | | | +| aMacMaxRetransmitDelay | Random backoff shall be lower than this value | 40 ms | | | | + +The MAC determines if the PHY is configured for channel configurations 1, 2, or channel configuration 3 operation by evaluating the RF profile mappings configured via the *macMapPhyChannel\** MAC MIB parameters and the RF profile table defined for the PHY. + +#### A.4.3.2 MAC MIB attributes + +The MAC MIB comprises the attributes required to manage the MAC layer. Each of these attributes can be read or written using the MLME-GET.request and MLME-SET.request primitives, respectively. The attributes contained in the MAC MIB are presented in Table A.49. + +**Table A.49 – MAC MIB attributes** + +| Attribute | Type | Range | Description | Default | +|----------------------------|------------|-------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------| +| macCCARetryDuration | Integer | aMacMinCCARetryDuration – infinite | The duration of clear channel access assessment | ~ 1100 ms | +| macHomeID | Byte Array | 0x00000000..
0xFFFFFFFF | The HomeID is the unique domain identifier | (random) | +| macNodeID | Byte | 0x00..0xFF | The NodeID is the address of the individual nodes in a domain | 0x00 | +| macPromiscuousMode | Boolean | TRUE or FALSE | This indicates whether the MAC layer is in a promiscuous (receive all) mode. A value of TRUE indicates that the | FALSE | + +**Table A.49 – MAC MIB attributes** + +| Attribute | Type | Range | Description | Default | +|--------------------------|---------|-----------------------------------|-------------------------------------------------------------------------------------------------------|---------| +| | | | MAC layer accepts all frames received from the PHY | | +| macRxOnWhenIdle | Boolean | TRUE or FALSE | This indicates whether the MAC layer is to enable its receiver at any time | FALSE | +| macMapPhyChannelA | Integer | Available RF profiles (Table A.1) | Apply RF profile to channel A. Parameter maps directly to the PHY MIB parameter phyMapChannelA | – | +| macMapPhyChannelB | Integer | Available RF profiles (Table A.1) | Apply RF profile to channel B. Parameter maps directly to the PHY MIB parameter phyMapChannelB | – | +| macMapPhyChannelC | Integer | Available RF profiles (Table A.1) | Apply RF profile to channel C. Parameter maps directly to the PHY MIB parameter phyMapChannelC | – | + +### A.4.4 MAC functional description + +This clause provides a detailed description of the MAC functionality. Throughout this clause, the receipt of an MPDU is defined as the successful receipt of an incoming MPDU from the RF media to the PHY and the successful verification of the FCS by the MAC layer, as described in clause A.4.2.8. + +#### A.4.4.1 Transmission, reception and ACK + +This clause describes the fundamental procedures for transmission, reception, and ACK. + +##### A.4.4.1.1 Clear channel access + +The MAC layer shall request the channel status from the PHY layer. + +A PLME-GET-CCA.request message is used to evaluate the channel. A PLME-GET-CCA.confirm message returns the current channel status. + +If the MAC layer finds the channel busy for a period of *macCCARetryDuration* times the transmission has failed. This shall be indicated to the network layer via the MD-DATA.confirm primitive with a status of NO\_CCA (see clause A.4.1.1.2). + +##### A.4.4.1.2 Transmission + +To avoid RF collisions the MAC layer shall perform a CCA before transmitting. If the channel is found idle, the MPDU may be transmitted. The Src HomeID and Src NodeID field shall identify the sending node and the Dst NodeID shall identify the Dst node. + +##### A.4.4.1.3 Reception and rejection + +Each node may choose whether the MAC layer is to enable its receiver during idle periods. During these idle periods, the MAC layer shall still service TRX task requests from the network layer. A TRX task shall be defined as a transmission request, a reception request, or a clear channel access detection. On completion of each TRX task, the MAC layer shall request that the PHY enables or disables its receiver, depending on whether *macRxOnWhenIdle* is set to TRUE or FALSE, respectively. + +Due to the broadcast nature of radiocommunications, a node is able to receive and decode transmissions from all nodes that are operating on the same channel(s). The MAC layer shall be able to filter incoming frames and present only the frames that are of interest to the upper layers. + +In promiscuous mode, the MAC layer shall pass all MPDUs directly to the network layer. If the MAC layer is not in promiscuous mode (i.e., *macPromiscuousMode* is set to FALSE), it shall only accept MPDUs and issue an MD-DATA.indication to the network layer if the MPDU header contains the HomeID and NodeID of the receiving node. MPDUs shall also be accepted if addressed to the broadcast address or if the NodeID is included in a multicast header. + +If the frame type subfield indicates a singlecast frame and the ACK request subfield of the frame control field is set to 1, the MAC layer shall send an ACK frame. + +The MAC layer shall be able to receive beam fragments and forward these to higher layers. + +###### A.4.4.1.3.1 RX filtering + +An MPDU shall be discarded if the received MPDU has an invalid FCS value. + +An MPDU shall be discarded if it has a length field less than 9 or greater than the maximum size values indicated in Tables A.47 and A.48. + +##### A.4.4.1.4 Use of ACK + +A singlecast MPDU may be sent with the ACK request subfield of the frame control field set to 1. Any multicast or broadcast frame shall be sent with the ACK request subfield set to 0. + +Sequence number checking shall be applied to ACK handling. Refer to clause A.4.2.3.7. + +###### A.4.4.1.4.1 No ACK + +An MPDU transmitted with its ACK request subfield set to 0 shall not be acknowledged by its intended recipient. The originating node shall assume that the transmission was successful. The sequence diagram in Figure A.30 shows the scenario for transmitting a single MPDU without requiring an ACK. + + + +The diagram illustrates the interaction between four entities: Source network layer, Source MAC layer, Destination MAC layer, and Destination network layer. The sequence of messages is as follows: 1. The Source network layer sends an MD-DATA.request (ACK = 0) to the Source MAC layer. 2. The Source MAC layer sends a Data frame to the Destination MAC layer. 3. The Source MAC layer sends an MD-DATA.confirm back to the Source network layer. 4. The Destination MAC layer sends an MD-DATA.indication to the Destination network layer. The diagram is labeled G.9959(15)\_FA.30. + +Sequence diagram for successful transmission without ACK + +Figure A.30 – Successful transmission an ACK + +###### A.4.4.1.4.2 ACK + +A singlecast MPDU transmitted with the ACK request subfield of its MPDU control field set to 1 shall be acknowledged by the recipient. If the intended recipient correctly receives the MPDU, it shall + +return an ACK MPDU. Only the singlecast MPDU may be sent with the ACK request subfield set to 1. For other frame types the ACK request subfield shall be ignored by the intended recipient. + +The transmission of an ACK MPDU shall not commence before *aPhyTurnaroundTimeRXTX* symbols have elapsed after the reception of the last symbol of the frame. Refer to clause A.3.1.14. + +The sequence diagram in Figure A.31 shows the transmission of an acknowledged singlecast MPDU. + + + +``` + +sequenceDiagram + participant SNL as Source network layer + participant SML as Source MAC layer + participant DML as Destination MAC layer + participant DNL as Destination network layer + Note right of DNL: G.9959(15)_FA.31 + SNL->>SML: MD-DATA.request (ACK = 1) + SML->>DML: Data frame (ACK = 1) + DML->>SML: ACK + SML->>SNL: MD-DATA.confirm + DML->>DNL: MD-DATA.indication + +``` + +Sequence diagram showing successful transmission with ACK. The diagram involves four lifelines: Source network layer, Source MAC layer, Destination MAC layer, and Destination network layer. The sequence of messages is: 1. Source network layer sends MD-DATA.request (ACK = 1) to Source MAC layer. 2. Source MAC layer sends Data frame (ACK = 1) to Destination MAC layer. 3. Destination MAC layer sends ACK back to Source MAC layer. 4. Source MAC layer sends MD-DATA.confirm to Source network layer. 5. Destination MAC layer sends MD-DATA.indication to Destination network layer. The diagram is labeled G.9959(15)\_FA.31. + +**Figure A.31 – Successful transmission with ACK** + +###### A.4.4.1.4.3 Retransmission + +A node that sends a singlecast MPDU with its ACK request subfield set to 1 shall wait for a minimum of *aMacMinAckWaitDuration* symbols for the corresponding ACK MPDU to be received. If an ACK MPDU is received within *aMacMinAckWaitDuration* symbols and contains the correct HomeID and Src NodeID, the transmission is considered successful, and no further action shall be taken by the originator. If an ACK MPDU is not received within *aMacMinAckWaitDuration* symbols the transmission attempt has failed. The originator shall repeat the process of transmitting the MPDU and waiting for the ACK MPDU up to *aMacMaxFrameRetries* times. Before retransmitting the node shall wait for a random backoff period (see clause A.4.4.1.4.4). + +If an ACK MPDU is still not received after *aMacMaxFrameRetries* retransmissions, the MAC layer shall assume the transmission has failed and notify the network layer of the failure. This shall be done via the MD-DATA.confirm primitive with a status of NO\_ACK (see clause A.4.1.1.2). + +###### A.4.4.1.4.4 Random backoff + +If a singlecast MPDU with its ACK request subfield set to 1 or the corresponding ACK MPDU is lost or corrupted, the singlecast MPDU shall be retransmitted. The MAC layer collision avoidance mechanism prevents nodes from retransmitting at the same time. The random delay shall be calculated as a period in the interval *aMacMinRetransmitDelay... aMacMaxRetransmitDelay*; Refer to Table A.48. + +##### A.4.4.1.5 Idle mode + +If the MLME is requested to set *macRxOnWhenIdle* to TRUE the PHY shall enter RX mode and stay in RX mode when a MPDU has been transmitted (AL). This is achieved when the MLME issues the PLME-SET-TRX-STATE.request primitive with a state of RX\_ON. + +If the MLME is requested to set *macRxOnWhenIdle* to FALSE, the PHY shall disable its receiver when a MPDU has been transmitted. This is achieved by the MLME issuing the PLME-SET-TRX-STATE.request primitive with a state of TRX\_OFF. + +#### A.4.4.2 Transmission scenarios + +Due to the imperfect nature of the radio medium, a transmitted MPDU does not always reach its intended destination. Figures A.32 to A.34 illustrate three different data transmission scenarios: + +- **Successful transmission.** The originating MAC layer transmits the MPDU to the recipient via the PD service. The originating MAC layer waits for *aMacMinAckWaitDuration* symbols. The Dst MAC layer receives the MPDU, returns an ACK MPDU, and passes the MPDU to the next higher layer. The originating MAC layer receives the ACK MPDU. The data transfer is now complete, and the originating MAC layer issues a success confirmation to the network layer. + + + +``` + +sequenceDiagram + participant SNL as Source network layer + participant SML as Source MAC layer + participant DML as Destination MAC layer + participant DNL as Destination network layer + + SNL->>SML: MD-DATA.request (AckReq = 1) + SML->>DML: Data frame (AckReq = 1) + DML->>SML: ACK + SML->>SNL: MD-DATA.confirm (SUCCESS) + DML->>DNL: MD-DATA.indication + +``` + +Sequence diagram for successful transmission scenario. It shows four lifelines: Source network layer, Source MAC layer, Destination MAC layer, and Destination network layer. The Source network layer sends an MD-DATA.request (AckReq = 1) to the Source MAC layer. The Source MAC layer sends a Data frame (AckReq = 1) to the Destination MAC layer. The Destination MAC layer receives the frame and sends an ACK back to the Source MAC layer. The Source MAC layer receives the ACK and sends an MD-DATA.confirm (SUCCESS) to the Source network layer. The Destination MAC layer also sends an MD-DATA.indication to the Destination network layer. The diagram is labeled G.9959(15)\_FA.32. + +**Figure A.32 – Successful transmission scenario** + +- **Lost MPDU.** The originating MAC layer transmits the MPDU to the recipient via the PD service. The originator MAC layer waits for *aMacMinAckWaitDuration* symbols. The destination MAC layer does not receive the MPDU, and therefore does not return an ACK MPDU. The timer of the originator MAC layer expires. The transmission has failed and the originator retransmits the MPDU. This sequence is repeated up to *aMacMaxFrameRetries* times. If transmissions fail a total of $(1 + aMacMaxFrameRetries)$ times, the originator MAC layer issues a failure confirmation to the network layer. + + + +``` + +sequenceDiagram + participant SNL as Source network layer + participant SML as Source MAC layer + participant DML as Destination MAC layer + participant DNL as Destination network layer + + SNL->>SML: MD-DATA.request + SML-x DML: Data frame + loop Retry frame transmission up to aMinFrameRetries times. + SML->>SML: + end + SML-x DML: Data frame + SML->>SNL: MD-DATA.confirm (NO_ACK) + +``` + +Sequence diagram for lost MPDU scenario. It shows four lifelines: Source network layer, Source MAC layer, Destination MAC layer, and Destination network layer. The Source network layer sends an MD-DATA.request to the Source MAC layer. The Source MAC layer attempts to send a Data frame, but it is lost (indicated by an 'X'). The Source MAC layer then enters a retry loop, labeled 'Retry frame transmission up to aMinFrameRetries times.' with a self-call symbol. After the retries, the Source MAC layer sends another Data frame, which is also lost. Finally, the Source MAC layer sends an MD-DATA.confirm (NO\_ACK) to the Source network layer. The diagram is labeled G.9959(15)\_FA.33. + +**Figure A.33 – Lost MPDU scenario** + +- **LostAck MPDU.** The originating MAC layer transmits the MPDU to the recipient via the PD service. The originating MAC layer waits for *aMacMinAckWaitDuration* symbols. The destination MAC layer receives the MPDU, returns an ACK MPDU back to the originator, and passes the MPDU to the network layer. The originating MAC layer does not receive the ACK MPDU and its timer expires. The transmission has failed, and the originator retransmits the MPDU. If transmissions fail a total of $(1 + aMacMaxFrameRetries)$ times, the MAC layer issues a failure confirmation to the network layer. + + + +``` + +sequenceDiagram + participant SNL as Source network layer + participant SML as Source MAC layer + participant DML as Destination MAC layer + participant DNL as Destination network layer + + SNL->>SML: MD-DATA.request + SML->>DML: Data frame + DML->>DNL: MD-DATA.indication + Note right of DML: ACK (lost) + Note left of SML: Retry frame transmission up to aMinFrameRetries times. + SML->>SNL: MD-DATA.confirm (NO_ACK) + +``` + +G.9959(15)\_FA.34 + +Sequence diagram illustrating a 'Lost ACK MPDU scenario'. It shows four lifelines: Source network layer, Source MAC layer, Destination MAC layer, and Destination network layer. The Source network layer sends an MD-DATA.request to the Source MAC layer. The Source MAC layer transmits a 'Data frame' to the Destination MAC layer. The Destination MAC layer receives the frame and sends an 'MD-DATA.indication' to the Destination network layer. The Destination MAC layer also attempts to send an 'ACK' back to the Source MAC layer, but this ACK is lost (indicated by an 'X'). Upon receiving no ACK, the Source MAC layer performs 'Retry frame transmission up to aMinFrameRetries times.' (indicated by a loop with a cross symbol). Finally, the Source MAC layer sends an 'MD-DATA.confirm (NO\_ACK)' back to the Source network layer. A label 'G.9959(15)\_FA.34' is present at the bottom right of the diagram. + +**Figure A.34 – Lost ACK MPDU scenario** + +# Bibliography + +- [b-ITU-T X.210] Recommendation ITU-T X.210 (1993) | ISO/IEC 10731: 1994, *Information technology – Open Systems Interconnection – Basic Reference Model: Conventions for the definition of OSI services.* + + + + + +# 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.9970-200901-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4379fe44cc1d732f7b269779fe145e4b466176e --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a44cb0245b054a4845c18a32f4258c13a4ab02538459304830f199768f850b3 +size 51046 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f40979c4fb9313347df3553e080f02cfe57d2a76 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db84e1aa1ff0e5b60413ee9b57e387c3b29db3e78c8aad62a1f03f8da683823b +size 32314 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02d6ef93359815410e54c2b548f0f122c0a46f89 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dc17e0158a64acd009dd90eb5b1df5009abbb38ba14beceb47ec912b9c07449 +size 81797 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b87b2b6e7c7c9a70c7e6365900f2c1e0a122358e --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69eba0498d675c6ce0fc5b3c35d1a50d6abbd74854d7b2a598b160b3375fbba3 +size 56737 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afe21ad78d38b47f58756cea649b90d7d3b13f1b --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94c8d88f3b8548e997a226ee1dab11a501aa1d92de8e7ff3105512ab1e85ca0b +size 34889 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2ae8d99ffa7fe636a7d19ce432ee7eaa5b74f59 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d53af7314ba2adc2aa07660bfbed176dd25c5ca90d382ce97541fef4a59c777 +size 91391 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a83a9d4fa9783fce724c24d4de6b3c03c1422a82 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6e92f36863d417d57a41ed1f38392ac139f2c84f055d8633e19a4dd9c95acfa +size 91236 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fffe0125c7276b276a275013bdeb6a16e5b6ce19 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e203f686e7b037ff657bd7b56bc1623d38765a1114c20d86463b4b8e3650234 +size 9769 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..771132d5b09b771615879351abd80dbc20668cb5 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a815b89f88d03b332294dc9343607087eeac74916173c195e70efbdde4e70e2 +size 107203 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50439646fd9265a204ef599e71e304ebce5de6d0 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97024c83c6940b9d8c5d842995d14083a18f327b3c6dbf240607bf248d2608ef +size 104900 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fa5890d7660182e6ea2597ef6f4f97b38dc528f --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2759a9d96780947e8b6f3adf0ab0278c50853804bbc381405464bb9b4dd91ad +size 6986 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cb1a44f036977779648b046044121a6f75827d1 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00557c50a14d4372743dc3514ed8a8200a6392e3a9458e28d0c20bda400a3fb0 +size 61168 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/9b686adccf125267a013fa25721231a3_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1118f4084c11a57ee9a6eb463881b3a3133120d2 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f87d555a6b865c00081084d570a14f762b9d89cc4618a7764264b2fc53b3bbbb +size 59797 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fb423ec915d380b2982be40cbe0595981e6ebed --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:678474049789cc57c472c3a70b48e7f5456e38d462681ab5e067975811286000 +size 38671 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..423633e99a090adaa4268482fbe348f5596b71ba --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a1e65a6259f14501efb089729eec2140f54937b56ff7e90c32af0020031deab +size 134889 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d666a2f2cb3e190408d85e9b05a7560620292a59 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6178c4ceb1e774b93640f447db2a97a5fa74359f7d420384b9c3e6848932b77b +size 15695 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bac7ca2e03a32747aea471d043760c62e0171cfe --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49ba5fcd91e649fa3537e2ec3487213d1d04e084ae01e463a9ed3f9c935d0399 +size 19224 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f4ef96f52e8ad7be680795366d265b8a2fa693f --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:131fb37cfb3a0d0d4206a998fe409aafee8aeb41027fe3e9559912a51bf8d2a0 +size 75388 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..591e004ae39970e0c584f2ea047d875ef7839e79 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1baeb5ac147625c71e4747802baaa467af824a8cade8984be354e0c541b1cc11 +size 59337 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce7d01cc04778e870cf218e8a0f579c1b8f5fb0c --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12450bf97d17a91861b2deb9290b7360c221c1c04836a55b6dab090612be7b51 +size 57538 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91b0cb8543d9070ae587644b7aa9cc1cd5c19674 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10225a1ea170baf6da5c836a2bb0d2a49de5d9eb63c367a6f3a3728724ef982a +size 57320 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/G/T-REC-G.9970-200901-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64263352d7cb8d96889327e07613b16338a608c1 --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70afc393a46e721c38328928ad3f73648194077f6a5d1a891a39b30454c87878 +size 56494 diff --git a/marked/G/T-REC-G.9970-200901-I_PDF-E/raw.md b/marked/G/T-REC-G.9970-200901-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d4a70b17c89a4e673f81cc647921a7ee466ca31e --- /dev/null +++ b/marked/G/T-REC-G.9970-200901-I_PDF-E/raw.md @@ -0,0 +1,684 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.9970** + +(01/2009) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Access networks – In premises networks + +# --- **Generic home network transport architecture** + +Recommendation ITU-T G.9970 + + + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, symbolizing global connectivity and telecommunications. The text "ITU" is prominently displayed in blue, with "International Telecommunication Union" written in smaller blue text to the right. + +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 | +| 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 | +| In premises networks | G.9950–G.9999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T G.9970** + +# **Generic home network transport architecture** + +## **Summary** + +Recommendation ITU-T G.9970 describes the generic architecture for home networks and their interfaces to the operators' broadband access networks. + +## **Source** + +Recommendation ITU-T G.9970 was approved on 13 January 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 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
Document | Aggregate type AGW | Separate type AGW | | +|-------------------------|--------------------|-------------------|-----------| +| | NT/AGTF/AGAF | NT | AGTF/AGAF | +| [TR-094] | B-NT + RG | B-NT | RG | +| [ITU-T H.610] | VTP/D | – | – | +| [ITU-T J.190] | HA | – | – | + +## 6.3 Relationship between the home network architecture for the transport layer and that of the application layer + +The main objective of the home network architecture for the transport layer is to ensure that communication in the application layer can be carried over the transport layer. To better understand the relationship between two home network architectures, one physical configuration is provided in Figure 6-8. This includes the following features. + +- The primary terminal contains both an IP terminal type a) and an application layer device function (ALDF), while the secondary terminal contains both a non-IP terminal and an ALDF. AGW, which is the aggregated type in this example, contains NT, AGTF and AGAF. + +- AGW terminates the public IP address and interacts with an IP terminal type a) by a local IP address, while IP terminal type a) interacts with the non-IP terminal by a non-IP (L3) protocol. Both the IP terminal type a) and the non-IP terminal lie within the transport layer in the home network. +- On the other hand, ALDF in the primary terminal interacts with functions in the application layer of the carrier's network via the AGAF in the AGW. It also interacts with ALDF in the secondary terminal at the application level. +- The primary domain is provided over an IP home network, while the secondary domain is provided over a non-IP home network. + + + +The diagram illustrates a physical configuration based on two generic home architectures. It is divided into two main sections: **Carrier's network** and **Home network**. + +- Carrier's network:** + - Contains an **Application layer** (green box) and a **Transport layer (access network)** (orange box). + - The **Transport layer** contains an **IP router** (green box). +- Home network:** + - AGW (Aggregated Gateway):** + - Contains **AGAF** (Application Gateway Function) and **AGTF** (Aggregated Transport Function). + - AGTF** contains two **IP** blocks and a **LANT** block. + - An **NT** block is also present in the AGW. + - Primary terminal:** + - Contains **Application layer device functions**. + - Contains an **IP terminal (type a)**, which includes **IP** and **L3** components. + - Below the IP terminal are **L2/L1** components. + - Secondary terminal:** + - Contains **Application layer device functions**. + - Contains a **Non-IP terminal**, which includes **L3** and **L2/L1** components. + - Network Domains:** + - Primary domain** and **IP home network** (blue shaded areas) connect the AGW to the Primary terminal. + - Secondary domain** and **Non-IP home network** (blue shaded areas) connect the Primary terminal to the Secondary terminal. + +G.9970(09)\_F6-8 + +Figure 6-8: One physical configuration based on two generic home architectures. The diagram shows the Carrier's network connected to a Home network. The Home network includes an AGW, a Primary terminal, and a Secondary terminal. Data flows through various layers including Application and Transport layers across these components. + +**Figure 6-8 – One physical configuration based on two generic home architectures** + +Considering the above, you can find three typical flows in layer 3, as shown in Figure 6-9. Note that this figure shows a physical configuration; specifically, the AGW is the aggregated type device, while the IP terminal (type a) is the device that contains the IP terminal (type a) function. + +- Flow 1: IP terminal (type a) acting as the primary terminal receives packets from the AGW via the IP home network and then distributes them to the non-IP terminal acting as the secondary terminal via the non-IP home network. +- Flow 2: IP terminal (type b) acting as the primary terminal receives packets from the AGW via the IP home network and then distributes them to the IP terminal (type c) acting as the secondary terminal, also via the IP home network. Note that IP terminals type b) and type c) can be combined. In such a case, the IP terminal (types b and c) acts as both primary and secondary terminal. +- Flow 3: The non-IP GW receives packets from the AGW via the IP home network and then forwards them to the non-IP terminal acting as primary terminal via the non-IP home network. + +Note that Appendix I shows various cases applying this generic home network architecture for the transport layer in home networks. + + + +AGTF: Access Gateway Transport layer Function +NT: Network Termination + +G.9970(09)\_F6-9 + +Figure 6-9: Three typical flows over the generic home network transport physical architecture. The diagram shows an Access network connected to an AGW (Access Gateway) which contains NT (Network Termination) and AGTF (Access Gateway Transport layer Function). From the AGW, three flows (Flow 1, Flow 2, Flow 3) originate. Flow 1 goes to an IP home network, which then connects to an IP terminal (type a). Flow 2 goes to an IP terminal (type b). Flow 3 goes to a Non-IP GW, which then connects to a Non-IP home network, which finally connects to a Non-IP terminal. There is also a direct connection from the AGW to another Non-IP terminal. + +**Figure 6-9 – Three typical flows over the generic home network transport physical architecture** + +Figure 6-10 summarizes the two layered generic home network models. AGW is a physical device that contains at least AGTF and AGAF. Moreover, it may also contain NT function as optional. Both primary terminal and secondary terminal are physical devices that contain application layer device functions as well as transport layer terminal functions, such as IP terminal or non-IP terminal. The primary terminal may contain either IP terminal or non-IP terminal. Similarly, the secondary terminal may also contain either IP terminal or non-IP terminal. + + + +HN: Home Network +NT: Network Termination +AGAF: Access Gateway Application layer Function +AGTF: Access Gateway Transport layer Function + +G.9970(09)\_F6-10 + +Figure 6-10: The conceptual diagram of two layered generic home network models. The diagram is divided into two horizontal layers: the Application layer model (top) and the Transport layer model (bottom). The Application layer model shows three main components: Access Gateway (AGW), Primary terminal, and Secondary terminal. The AGW contains AGAF (Access Gateway Application layer Function). The Primary terminal and Secondary terminal each contain Application layer device functions. The Transport layer model shows the AGW containing NT (Network Termination) and AGTF (Access Gateway Transport layer Function). The Primary terminal and Secondary terminal each contain IP/non-IP terminal functions. Below the Primary terminal is an IP terminal and a Non-IP gateway. Below the Secondary terminal is a Non-IP terminal. On the left, the Transport layer model also shows IP HN (Home Network) and Non-IP HN. A legend at the bottom right defines the symbols: Network category (solid line), Device (solid line), Device function (solid line), and Device function (option) (dashed line). + +**Figure 6-10 – The conceptual diagram of two layered generic home network models** + +# 7 Possible demarcation points + +As described in clause 6, service is provided to the primary terminal in the application layer, which is supported by either the IP terminal or the non-IP terminal in the transport layer. Therefore, the interfaces to reach each terminal are potential demarcation points between the user and operator domains of responsibility. Possible demarcation points for an IP terminal are described in clause 7.1, while those for a non-IP terminal are described in clause 7.2. One of these demarcation points would be selected by a user and an operator, considering the service model deployed. Moreover, we shall take into account that there are two types of AGW, aggregation type and separate type. + +## 7.1 Possible demarcation points for IP terminals + +Points A, B, C, D1 and D2 in Figure 7-1 are the possible demarcation points for an IP terminal (type a) and IP terminal (type b), both of which act as primary terminal. As both non-IP terminal and IP terminal (type c) do not act as primary terminal, the interfaces to reach each terminal are shown as dotted lines in order to indicate that they are not possible demarcation points. + + + +Figure 7-1: Possible demarcation points for IP terminals. The diagram shows an 'Access network' connected to an 'NT' (Network Terminal) at point A. The 'NT' is part of an 'Aggregate type AGW' (indicated by a bracket over NT and AGTF) and is connected to an 'AGTF' (Access Gateway Terminal Function) at point B. The 'AGTF' is part of a 'Separate type AGW' (indicated by a bracket under AGTF) and is connected to an 'IP home network' at point C. Inside the 'IP home network', there are three terminals: 'IP terminal (type a)' connected at point D1, 'IP terminal (type b)' connected at point D2, and 'IP terminal (type c)' connected via a dotted line. The 'IP terminal (type a)' is connected to a 'Non-IP home network' and then to a 'Non-IP terminal' via dotted lines. The text 'G.9970(09)\_F7-1' is in the bottom right corner. + +Figure 7-1 – Possible demarcation points for IP terminals + +## 7.2 Possible demarcation points for non-IP terminals + +Existing non-IP services should be provided to the non-IP terminals, such as TV, STB, telephone, PC peripherals, etc., that do not have IP capability. Points A, B, C, E, F, G and H in Figure 7-2 are the possible demarcation points for non-IP terminals. + + + +Figure 7-2: Possible demarcation points for non-IP terminals. The diagram shows an 'Access network' connected to an 'NT' (Network Terminal) at point A. The 'NT' is part of an 'Aggregate type AGW' (indicated by a bracket over NT and AGTF) and is connected to an 'AGTF' (Access Gateway Terminal Function) at point B. The 'AGTF' is part of a 'Separate type AGW' (indicated by a bracket under AGTF) and is connected to an 'IP home network' at point C. From the 'IP home network', the path continues at point E to a 'Non-IP GW' (Gateway), then at point F to a 'Non-IP home network', and finally at point G to a 'Non-IP terminal'. There is also a direct connection from the 'Access network' at point H to another 'Non-IP terminal'. The text 'G.9970(09)\_F7-2' is in the bottom left corner. + +Figure 7-2 – Possible demarcation points for non-IP terminals + +# 8 High level requirements + +## 8.1 QoS control + +The functionality to realize QoS control over IP networks is important in order to accomplish stable quality in case of offering streaming-based multimedia services on the IP network. One QoS control domain can be defined, at the edge of which two kinds of QoS services: parameterized QoS and prioritized QoS. [ITU-T Y.1541] specifies IP-based parameterized QoS. Parameterized QoS is realized by some control protocols, such as SIP utilized in NGN, and RSVP mentioned in [ITU-T J.190]. Dynamic parameterized QoS control can be provided by using these protocols, while static parameterized QoS can be provided by management functions. On the other hand, prioritized QoS is realized by DSCP for IP or Ethernet VLAN, which attaches a priority level to each packet. QoS mechanisms described in [TR-094] requirements are all for prioritized QoS. Moreover, [TR-094] includes the configuration of many QoS parameters. + +In case of studying the requirements for the access GW (or AGW) to realize end-to-end QoS control between two remote IP terminals in different IP home networks via a network provider's network, we shall consider that they communicate with each other over multiple QoS control domains. We can identify three types of service scenarios in terms of QoS control domains. + +- Type 1: One QoS control domain exists for the IP home network, but there is no QoS control domain for the network provider's network including the access network. +- Type 2: QoS control domains exist both for the network provider's network, including the access network, and for the IP home network. +- Type 3: One QoS control domain exists through the network provider's network, including the access network as well as the IP home network. + +Type 1 is the non-NGN case, in which the network provider's network, including the access network, provides only best-effort service, which means that it does not provide any QoS control, such as parameterized or prioritized. As QoS control is provided only within each IP home network, end-to-end QoS control between two remote IP terminals cannot be achieved. On the other hand, types 2 and 3 apply to the NGN case. + +Figure 8-1 shows type 2. A QoS mapping function is required for the access GW, because the QoS control in one network provider's network including the access network, and the two IP home networks may be different from each other. After QoS mapping, admission control may be performed by the access GW to check whether the network resources are enough to achieve the required QoS. After the communication is established between the two remote IP terminals, some traffic control, such as priority control, policing or shaping, will be also performed by the access GW. + +The QoS mapping should be performed, considering the following cases: + +- One case is that the access network is IP (layer 3) QoS control domain, while the IP home network is an Ethernet (layer 2) QoS control domain. Another case is the reverse one, with IP QoS in the home network and Ethernet QoS in the access network. In these two cases, layers 3 and 2 QoS mapping should be performed. +- Even if both the access network and the IP home network are either IP (layer 3) or Ethernet (layer 2) QoS control domains, one may be a parameterized QoS control domain, while the other may be a prioritized QoS control domain. +- Even if both the access network and the IP home network are parameterized QoS control domains, each may have different QoS specifications. + +Figure 8-1 also shows Type 3. No QoS mapping function is required for the access GW, because one unique QoS control service is provided through the IP home network as well as the network + +provider's network, including the access network. However, admission control, as well as some traffic control functions, may be needed for the access GW. + + + +**Type 2: Different QoS control** + +**Type 3: One unique QoS control** + +Diagram of Type 2 QoS control showing three domains: A, B, and C. Domain A contains an IP home network and an Access GW. Domain B contains two Access networks connected by a dashed line. Domain C contains an Access GW and an IP home network. The Access GW in Domain A is connected to the first Access network in Domain B. The second Access network in Domain B is connected to the Access GW in Domain C. Below each Access GW, a callout box lists: ✓QoS mapping, ✓Admission control (option), and ✓Traffic control. Diagram of Type 3 QoS control showing a single domain B. It contains an IP home network, an Access GW, two Access networks connected by a dashed line, another Access GW, and another IP home network. Below each Access GW, a callout box lists: ✓Admission control (option) and ✓Traffic control. A label G.9970(09)\_F8-1 is in the bottom right corner. + +**Figure 8-1 – QoS control for network provider's network and IP home networks** + +## 8.2 Device management + +As described in clause 7, the primary terminal in the application layer, which is the service end-point, is supported by either the IP terminal or the non-IP terminal in the transport layer. Therefore, the devices from the access network communicating with either the IP terminal or the non-IP terminal should be managed by a remote management server (RMS) owned by the network provider or service provider. Management functions include configuration, local monitoring and maintenance. + +The AGW will be directly managed by the RMS. The protocols to be used are the standard management protocols based on IP, such as ICMP and SNMP. Moreover, one more promising candidate is [TR-069 Amd.1] specified in Broadband Forum, which provides configuration and performance monitoring functions. Note that [TR-098] is a companion specification to [TR-069 Amd.1] and specifies configuration parameters for AGW. + +There will be two schemes to manage end devices, such as IP terminal, non-IP terminal or non-IP GW, as shown in Figure 8-2. Scheme A is the one in which RMS directly manages individual end devices, while scheme B is the one in which RMS only manages an AGW that manages individual end devices instead of RMS. Note that the AGW contains both NT and AGTF in this figure. + + + +The diagram illustrates two network architectures for remote device management. Both start with a Remote management server (RMS) connected to an Access network, which is connected to an AGW. In Scheme A, the AGW is connected to an IP home network containing an IP terminal and a Non-IP GW. The Non-IP GW is connected to a Non-IP home network containing a Non-IP terminal. In Scheme B, the AGW is connected to an IP home network containing an IP terminal and a Non-IP GW. The Non-IP GW is connected to a Non-IP home network containing a Non-IP terminal. The difference is that in Scheme B, the AGW manages the IP terminal and Non-IP GW, which in turn manage the Non-IP terminal. + +Scheme A: Direct remote end device management + +Scheme B: Indirect remote end device management via AGW + +G.9970(09)\_F8-2 + +Legend: + +- Standard management protocol (solid red line with double arrowheads) +- Proprietary management protocol (dashed red line with double arrowheads) + +Figure 8-2: Two schemes to remotely manage end devices. Scheme A shows direct management by the RMS, while Scheme B shows indirect management via the AGW. + +**Figure 8-2 – Two schemes to remotely manage end devices** + +As for scheme A, the protocols to manage IP terminals and non-IP GWs are the same ones used to manage AGW, described above. However, proprietary management protocols are applied for managing non-IP terminals because there is a non-IP home network before it. + +Scheme B can also use the standard management protocol based on IP, such as ICMP and SNMP, for the protocol between AGW and IP terminal or non-IP GW. Moreover, since this scheme requires plug and play to enhance usability, the specifications discussed in UPnP™ Forum (
- Value[0] – indicating no synchronization (0x00)
- Value[1] – pair number in the BTU-C and 0xFF in the BTU-R
- Value[2] – Aggregation group number in the BTU-C and 0xFF in the BTU-R
- [S1], [S2] to "NE Sync" state
- [S5] to "Wrong Config BTU-R" state
BTU-R is waiting for the BTU-C to get to "Full Sync" state (indicated by receiving events other than evSync events) | Sending evSync events with:
- Value[0] – indicating NE synchronization (0x01)
- Value[1] – the pair number
- Value[2] – the aggregation group number
- [S3], [S4] to "Full Sync" state
- [S6] to "Wrong Config BTU-C" state
- [S7] to "Sync Hunt" state
The BTU-R is not able to get the aggregation group number or the pair number | None | Sending evSync events with:
- Value[0] – NE sync (0x01)
- Value[1] – the pair number
- Value[2] – the aggregation group number
- [S7], [S8] to "Sync Hunt" state
There is wrong configuration:
The BTU-R is already connected to another Aggregation Group or the pair number assigned to this pair is already in use by the BTU-R | Waiting for evSync events with a different Aggregation Group number or pair number | Sending evSync events with:
- Value[0] – Wrong Config (0x80 or 0x81)
- Value[1] – the pair number
- Value[2] – the Aggregation Group number
- [S2] to "NE Sync" state
- [S7] to "Sync Hunt" state
- [S7] to "Sync Hunt" state
- [P1] to "Handshake" state
- [P2] to "Down" state
- [P3] to "Activation" state
- [P4] to "Down" state
- [P5] to "Synching to group" state
- [P6] to "Down" state
- [P7] to "Synching to group" state
- [P8] to "Synched to group" state
- [P6] to "Down" state
- [P9] to "Adding to group" state
- [P10] to "Lost sync to group" state
- [P11] to "Part of group" state
- [P10] to "Lost sync to group" state
- [P12] to "Remove from group" state
- [P6] to "Down" state
- [P13] to "Synching to group" state
- [P6] to "Down" state
- [P10] to "Lost sync to group" state
- [P13] to "Synching to group" state
- [G1] to "Diag" state
- [G2] to "Down" state
- [G3] to "Init" state
- [G4] to "Diag" state
- [G5] to "Up" state
- [G6] to "Pairs change" state
- [G7] to "Fast pairs removal" state
- [G4], [G5] to "Up" state
- [G7] to "Fast pairs removal" state
- [G8] to "Diag" state
- [G9] to "Up" state
- [G7] to "Fast pairs removal" state
- [G10] to "Down" state
- [G11] to "Diag" state
1 byte | Value [3:0]
4 bytes | | CRC
1 byte | +|--------------------|------------------------|--|---------------| + +G.998.3\_F19 + +**Figure 19/G.998.3 – Event format** + +- Operation code (Op. code) – Identifies the event, 1 byte. +- Value – Contains the information that is being carried by the event, 4 bytes. +- CRC – Is used to validate the correctness of the event, 1 byte. + +### 13.2.3 Types and values + +Table 7 specifies the event types and the values in the various event fields: + +**Table 7/G.998.3 – Event codes and values** + +| Op. code | Event name | Value [3:0] | Description | +|----------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0x00 | evNull | 0x00000000 | Null event. Shall be transmitted whenever there is no other event or message to transmit. | +| 0x01 | evFastChange | Bitmap of the pairs that shall be part of the multipair aggregation group after the change. This bitmap relates to the pair map after the pair discovery stage, according to the pair numbering used in the Value[1] byte of evSync event value. The MSB is transmitted first (in Value[3]) and the LSB is transmitted last (in Value[0]). | Fast change in the pairs that are part of the aggregation group. | +| 0x02 | evSyncChange | Bitmap of the pairs that shall be part of the multipair aggregation group after the change. This bitmap relates to the pair map after the pair discovery stage, according to the pair numbering used in the second byte of evSync event value. The MSB is transmitted first (in Value[3]) and the LSB is transmitted last (in Value[0]). | Synchronized (managed) change in the pairs that are part of the aggregation group. | +| 0x03 | evConfigSw | The number of super-frames that shall be sent before switching to the new configuration. | Configuration switch indication. Specifies the number of super-frames that shall be sent to the peer before switching to a new configuration. The configuration includes:
- – Dispatching table
- – Service configuration
- – FEC/Interleaver configuration
Value[2] – the number of the aggregation group. A value of 0xFF shall be used by the BTU-C when the pair is not assigned to an aggregation group, and by the BTU-R to indicate that a group number was not assigned to it yet.
Value[1] – the number of the pair in the aggregation group. A value of 0xFF shall be used by the BTU-C when the pair is not assigned to an aggregation group, and by the BTU-R to indicate that a pair number was not assigned to it yet. | | + +**Table 7/G.998.3 – Event codes and values** + +| Op. code | Event name | Value [3:0] | Description | +|----------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Value[0] – Synchronization status indication, with the following values:
0x00 – No synchronization
0x01 – Near end is synchronized
0x02 – Both near end and far end are synchronized
0x80 – The BTU-R already has different aggregation group number. This value shall be transmitted only by the BTU-R, in the case where the aggregation group number received by this pair is different from the number already received by other pairs.
0x81 – The BTU-R already has this pair number. This value shall be transmitted only by the BTU-R, in the case where the aggregation group number received by this pair is the same as already received by other pairs and the pair number received by this pair is already used by another pair. | Sync attempt. This event shall be sent during pair synchronization to the aggregation group. The value indicates whether the pair is already synchronized, the aggregation group number and the pair number. The payload data in this pair shall be repetitive 0xE2. | + +#### 13.2.3.1 CRC + +An 8-bit CRC shall be generated for each event data (not including the CRC field) and shall be transmitted in the CRC field as specified in 13.2.2. + +The encoding of the eight bits CRC field is defined by the generating polynomial $G(x) = x^8 + x^7 + x^2 + 1$ (which equals $(x^7 + x + 1)(x + 1)$ ). This code can detect single, double and triple bit errors (and will fail only on 4-bit errors and up). Mathematically, the CRC value corresponding to a given event message is defined by the following procedure: + +- The first 8 bits of the event message are complemented. +- The 40 bits of the event message are then considered to be the coefficients of a polynomial $M(x)$ of degree 39. The first bit of the event message corresponds to the $x^{39}$ term and the last bit of the event message corresponds to the $x^0$ term. +- $M(x)$ is multiplied by $x^8$ and divided by $G(x)$ , resulting in a remainder $R(x)$ of degree 7. +- The coefficients of $R(x)$ are considered to be an 8-bit sequence. +- The bit sequence is complemented and the result is the CRC. +- The 8 bits of the CRC value are placed in the CRC field of the event so that the $x^7$ term is located in the left most bit of the CRC field, and the $x^0$ term is located in the right most bit of the CRC field. The bits of the CRC are thus transmitted in the order $x^7, x^6, \dots, x^1, x^0$ . + +## 13.3 Messages + +### 13.3.1 Introduction + +Messages are variable size datagrams of low priority, dedicated to slow communication between peers to handle non time-critical data, such as inventory, configuration, performance monitoring, maintenance, etc. Messages are always transmitted on all the pairs that belong to an aggregation + +group. Similarly to Events, messages are SF aligned and their total size is always multiples of 6 bytes. + +The total message length is variable, between 6 and 126 ( $= 6 \times 21$ ) bytes, thus they can span multiple super-frames. The M/E indicator bit shall be set to '1' at the beginning of each SF during an entire message transmission. + +If the message is interrupted by an event in the middle, it shall be retransmitted. + +### 13.3.2 Format + +A message has the format shown in Figure 20. + + + +| | | | +|------------------|--------------------------------|-----------------| +| Length
1 byte | Msg body
[Msg length bytes] | CRC-8
1 byte | +|------------------|--------------------------------|-----------------| + +G.998.3\_F20 + +**Figure 20/G.998.3 – Message format** + +- Length – Specifies the length of the message body in bytes, 4..124. +- Msg body – Contains the message information, with length in bytes specified by the length field. Msg body contains Msg ID (first byte) which determines the format of the following data. +- CRC-8 – Used to validate the correctness of the message, 1 byte. + +### 13.3.3 Types and content + +The BCC messages are summarized in Table 8: + +**Table 8/G.998.3 – BCC messages** + +| Msg ID | Length (Msg body) | Message type | Initiating unit (BTU-C, BTU-R) | Description | +|--------|-------------------|----------------------------------------------|--------------------------------|----------------------------------------------------------| +| 0 | 4 | Unable To comply (UTC) | -C, -R | Responding unit was unable to comply with request | +| 1 | 4 | Inventory request | -C, -R | Request T DIM protocol version and vendor ID | +| 2 | 10 | Inventory response | -C, -R | T DIM protocol version and vendor ID response | +| 3 | 4 | Performance Monitor (PM)/ Statistics request | -C, -R | Used to request/initialize all T DIM layer PM/Statistics | +| 4 | 10 | PM/Statistics response | -C, -R | T DIM layer statistics (CRC-4/6/8 violations etc.) | +| 5 | Variable (4-124) | Service mapping request | -C, -R (Get only) | Get/Set mapping of service interface types | +| 6 | Variable (4-124) | Service mapping response | -C, -R | Mapping of service interface types | +| 7 | Variable (4-124) | TDM service configuration request | -C, -R (Get only) | Get/Set TDM service configuration | +| 8 | Variable (4-124) | TDM service configuration response | -C, -R | TDM service configuration | + +**Table 8/G.998.3 – BCC messages** + +| Msg ID | Length (Msg body) | Message type | Initiating unit (BTU-C, BTU-R) | Description | +|---------------|--------------------------|---------------------------------------------|---------------------------------------|-----------------------------------------------------| +| 9 | Variable (4-124) | Asynchronous service configuration request | -C, -R (Get only) | Get/Set asynchronous service configuration | +| 10 | Variable (4-124) | Asynchronous service configuration response | -C, -R | Asynchronous service configuration | +| 11 | 4 | FEC capability request | -C, -R (Get only) | Get/Enable/Disable FEC-IL | +| 12 | 4 | FEC capability response | -C, -R | FEC capability response, includes FEC-IL parameters | +| 13 | 4 | Pair mapping request | -C, -R | Request for logical to physical pair mapping | +| 14 | Variable (4-67) | Pair mapping response | -C, -R | Logical to physical pair mapping response | +| 15-127 | | Reserved | | Reserved | +| 128-255 | | Vendor specific | | Reserved for vendor specific messages | + +### 13.3.4 Message contents + +The contents of each message will be specified in the following clauses. + +If any message has a message length longer than expected and is received in a frame with a valid CRC, then the known portion of the message shall be used and the extra octets discarded. This will permit addition of new fields to existing messages and maintain backward compatibility. New data fields shall only be placed in reserved bits after the last previously defined data octet. + +Reserved bits and octets shall be filled with the value 0x0 for forward compatibility. + +Response messages may indicate Unable to Comply (UTC). Note that this is not an indication of non-compliance. UTC indicates that the responding unit was unable to implement the request. + +#### 13.3.4.1 Unable to comply + +The generic UTC message shall be sent back to the source unit in the event that the destination unit is unable to comply with the request. In this case, the definition of UTC is vendor dependent. Note that this message is not meant to replace the UTC bit in those response messages that contain a UTC bit. + +**Table 9/G.998.3 – Unable to comply** + +| Octet # | Content | Data type | Description | +|----------------|--------------------------|------------------|--------------------| +| 1 | MsgID = 0 | Message ID | | +| 2 | MsgID of request message | Message ID | | +| 3-4 | Reserved | | | + +#### 13.3.4.2 Inventory request + +Inventory request message is used to query inventory information specific to the aggregation layer at the far end. The response to this request shall be message ID 2. + +**Table 10/G.998.3 – Inventory request** + +| Octet # | Content | Data type | Description | +|---------|-----------|------------|-------------| +| 1 | MsgID = 1 | Message ID | | +| 2-4 | Reserved | | | + +#### 13.3.4.3 Inventory response + +The inventory response message is sent in response to the inventory request message (message ID 1). It reports inventory information specific to the aggregation layer of the source BTU. + +**Table 11/G.998.3 – Inventory response** + +| Octet # | Content | Data type | Description | +|---------|---------------|--------------|-----------------------------------------------------------------------------------------------------| +| 1 | MsgID = 2 | Message ID | | +| 2.4-7 | Major version | 1-15 | Major version of the TDM aggregation protocol. Current value = 1. | +| 2.0-3 | Minor version | 0-15 | Minor version of the TDM aggregation protocol. Current value = 0. | +| 3-10 | Vendor ID | octet string | Vendor ID of the TDM aggregation layer (ordered identically to the vendor ID in ITU-T Rec. G.994.1) | + +#### 13.3.4.4 PM/Statistics Request + +PM/Statistics request message is used to query the aggregation layer related PMs/Statistics at the far end. The response to this request shall be message ID 4. + +**Table 12/G.998.3 – PM/Statistics request** + +| Octet # | Content | Data type | Description | +|---------|-----------|----------------------------------|---------------------------------------------------------------------------------------| +| 1 | MsgID = 3 | Message ID | | +| 2 | Request | Unsigned integer 8 bits (uint 8) | 0 – Request PM/Statistics report
1 – Initialize all far end PM/Statistics counters | +| 3-4 | Reserved | | | + +#### 13.3.4.5 PM/Statistics response + +The PM/Statistics response message is sent in response to the PM/Statistics request message (message ID 3), or autonomously at BTU-R discretion. It reports statistics specific to the aggregation layer of the source BTU. + +**Table 13/G.998.3 – PM/Statistics response** + +| Octet # | Content | Data type | Description | +|---------|---------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| 1 | MsgID = 4 | Message ID | | +| 2,3 | CRC-4 Anomaly count | Unsigned integer 16 bits (uint 16) | Frame errors. Sum of CRC-4 errors on all pairs in the aggregation group, simultaneous errors on m lines shall be counted m times | +| 4,5 | CRC-6 Anomaly count | uint 16 | SF errors. Sum of all pairs in the aggregation group | +| 6,7 | CRC-8 Anomaly count | uint 16 | Number of corrupted Events/Messages, sum of all pairs in the aggregation group | +| 8-10 | Reserved | | | + +#### 13.3.4.6 Service mapping request + +Service mapping request message allows a BTU to query and control how service interfaces of the far end unit are mapped (by the service mux (Multiplexer)) into the bonding sub-blocks of the aggregated link. The response to this request shall be message ID 6. + +**Table 14/G.998.3 – Service mapping request** + +| Octet # | Content | Data type | Description | +|---------|----------------------------------------------------------|------------|--------------------------------------------------------------------------------------------------| +| 1 | MsgID = 5 | Message ID | Request the far end to send its service mapping | +| 2,7 | Request | bit (0-1) | 0 – Request report
1 – Set (BTU-C only) | +| 2,0-6 | Reserved | | | +| 3 | Number of Services (NS) | uint 8 | NS = 0..60 | +| 4 | Service type notation for service 1 ( $j = 1$ in 10.2) | uint 8 | Applicable for set only. Defines which service type to map into service 1 (highest priority) | +| 5 | Service type notation for service 2 ( $j = 2$ in 10.2) | uint 8 | Applicable for set only. Defines which service type to map into service 2 (2nd highest priority) | +| . | | | | +| . | | | | +| . | | | | +| NS+3 | Service type notation for service NS ( $j = NS$ in 10.2) | uint 8 | Applicable for set only. Defines which type to map into service NS (lowest priority) | + +Note that the service mapping is setting the service priority. Service mapping request message with request value 1 (Set) shall always be followed by the evConfigSw event, which provides synchronized change of the configuration at both the BTU-C and the BTU-R. + +The Service type notations values are: + +- 1) Clear Channel DS1; +- 2) Clear Channel E1; +- 3) Fractional DS1; +- 4) Fractional E1; + +- 5) DS3; +- 6) E3; +- 7) Clock transfer; +- 8) Ethernet; +- 9) ATM; +- 10) GFP. + +#### 13.3.4.7 Service mapping response + +The service mapping response message is sent in response to a service mapping request message (message ID 5). It reports which Service interfaces of the source BTU are mapped into the services in the aggregated link. + +**Table 15/G.998.3 – Service mapping response** + +| Octet # | Content | Data type | Description | +|---------|----------------------------------------------------------|------------|-----------------------------------------------------------------------| +| 1 | MsgID = 6 | Message ID | | +| 2 | Number of services (NS) | uint 8 | NS = 0..60 | +| 3 | Service type notation for service 1 ( $j = 1$ in 10.2) | uint 8 | Defines which service type maps into service 1 (highest priority) | +| 4 | Service type notation for service 2 ( $j = 2$ in 10.2) | uint 8 | Defines which service type maps into service 2 (2nd highest priority) | +| . | | | | +| . | | | | +| . | | | | +| NS+2 | Service type notation for service NS ( $j = NS$ in 10.2) | uint 8 | Defines which service type maps into service NS (lowest priority) | + +Current values for all parameters shall be returned in response to service mapping request with Request value 1 (Set), after they have been set to the requested values by evConfigSw event. + +#### 13.3.4.8 TDM service configuration request + +TDM service configuration request message allows a BTU to query and control the configuration of TDM services, if additional information is required to "Service mapping request" message. The response to this request shall be message ID 8. + +**Table 16/G.998.3 – TDM service configuration request** + +| Octet # | Content | Data type | Description | +|---------|-------------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------| +| 1 | MsgID = 7 | Message ID | Request the far end to send its TDM services configuration | +| 2.7 | Request | bit (0-1) | 0 – Request report
1 – Set (BTU-C only) | +| 2.0-6 | Reserved | | | +| 3 | Number of services (NS) | uint 8 | NS = 0..60 | +| 4 | P 1 | uint 8 | Number of sub-channels (P, see 10.2) if service 1 is of service type notations 3 (Fractional DS1) or 4 (Fractional E1), otherwise 0 | +| 5 | P 2 | uint 8 | Number of sub-channels (P, see 10.2) if service 2 is of service type notations 3 (Fractional DS1) or 4 (Fractional E1), otherwise 0 | +| . | . | | | +| . | . | | | +| . | . | | | +| NS+3 | P NS | uint 8 | Number of sub-channels (P, see 10.2) if service NS is of service type notations 3 (Fractional DS1) or 4 (Fractional E1), otherwise 0 | + +TDM service configuration request message with request value 1 (Set) shall always be followed by the evConfigSw event, which provides synchronized change of the configuration at both BTU-C and BTU-R. + +#### 13.3.4.9 TDM service configuration response + +The TDM service configuration response message is sent in response to a TDM service configuration request message (message ID 7). It reports the configuration of TDM services with addition information to "Service mapping request" message. + +**Table 17/G.998.3 – TDM service configuration response** + +| Octet # | Content | Data type | Description | +|---------|-------------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------| +| 1 | MsgID = 8 | Message ID | Service configuration message | +| 2.7 | Response | bit (0-1) | 0 – OK
1 – UTC | +| 2.0-6 | Reserved | | | +| 3 | Number of services (NS) | uint 8 | NS = 0..60 | +| 4 | P 1 | uint 8 | Number of sub-channels (P, see 10.2) if service 1 is of service type notations 3 (Fractional DS1) or 4 (Fractional E1), otherwise 0 | +| 5 | P 2 | uint 8 | Number of sub-channels (P, see 10.2) if service 2 is of service type notations 3 (Fractional DS1) or 4 (Fractional E1), otherwise 0 | +| . | . | | | +| . | . | | | +| . | . | | | +| NS+3 | P NS | uint 8 | Number of sub-channels (P, see 10.2) if service NS is of service type notations 3 (Fractional DS1) or 4 (Fractional E1), otherwise 0 | + +Current values for all parameters shall be returned in response to TDM service configuration request message with request value 1 (Set), after they have been set to the requested values by an evConfigSw event. + +#### **13.3.4.10 Asynchronous service configuration request** + +Asynchronous service configuration request message allows a BTU to query and control the configuration of asynchronous services, if additional information is required to "Service mapping request" message. The response to this request shall be message ID 10. + +**Table 18/G.998.3 – Asynchronous service configuration request** + +| Octet # | Content | Data type | Description | +|---------|------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | MsgID = 9 | Message ID | Request the far end to send its asynchronous services configuration | +| 2.7 | Request | bit (0-1) | 0 – Request report
1 – Set (BTU-C only) | +| 2.6 | Optional FCS for GFP encapsulation | bit (0-1) | 0 – None
1 – Use FCS | +| 2.0-5 | Reserved | | | +| 3 | Number of Services (NS) | uint 8 | NS = 0..60 | +| 4 | N 1 | uint 8 | Maximal number of service 1 bytes in bonding sub-block of 125 µs if service 1 is of service type notations 8 (Ethernet) or 9 (ATM) or 10 (GFP), otherwise 0 | +| 5 | N 2 | uint 8 | Maximal number of service 2 bytes in bonding sub-block of 125 µs if service 2 is of service type notations 8 (Ethernet) or 9 (ATM) or 10 (GFP), otherwise 0 | +| . | . | | | +| . | . | | | +| . | . | | | +| NS+3 | N NS | uint 8 | Maximal number of service NS bytes in bonding sub-block of 125 µs if service NS is of Service type notations 8 (Ethernet) or 9 (ATM) or 10 (GFP), otherwise 0 | + +Asynchronous service configuration request message with Request value 1 (Set) shall always be followed by the evConfigSw event, which provides synchronized change of the configuration at both BTU-C and BTU-R. + +#### 13.3.4.11 Asynchronous service configuration response + +The asynchronous service configuration response message is sent in response to an asynchronous service configuration request message (message ID 9). It reports the configuration of asynchronous services with additional information to the "Service mapping request" message. + +**Table 19/G.998.3 – Asynchronous service configuration response** + +| Octet # | Content | Data type | Description | +|---------|------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | MsgID = 10 | Message ID | Service Configuration message | +| 2.7 | Response | bit (0-1) | 0 – OK
1 – UTC | +| 2.6 | Optional FCS for GFP encapsulation | bit (0-1) | 0 – FCS not used
1 – FCS is used | +| 2.0-5 | Reserved | | | +| 3 | Number of services (NS) | uint 8 | NS = 0..60 | +| 4 | N 1 | uint 8 | Maximal number of service 1 bytes in bonding sub-block of 125 µs if service 1 is of service type notations 8 (Ethernet) or 9 (ATM) or 10 (GFP), otherwise 0 | +| 5 | N 2 | uint 8 | Maximal number of service 2 bytes in bonding sub-block of 125 µs if service 2 is of service type notations 8 (Ethernet) or 9 (ATM) or 10 (GFP), otherwise 0 | +| . | . | | | +| . | . | | | +| . | . | | | +| NS+3 | N NS | uint 8 | Maximal number of service NS bytes in bonding sub-block of 125 µs if service NS is of service type notations 8 (Ethernet) or 9 (ATM) or 10 (GFP), otherwise 0 | + +Current values for all parameters shall be returned in response to asynchronous service configuration request with Request value 1 (Set), after they have been set to the requested values by an evConfigSw event. + +#### 13.3.4.12 FEC capability request + +The FEC/interleaver capability is reported and negotiated during service setup via BCC messages. FEC capability request is used to query and control FEC capability at the far end. The response to this request shall be message ID 12. + +FEC capability request message with disable or enable request values shall always be followed by the evConfigSw event, which provides synchronized change of the configuration at both BTU-C and BTU-R. The FEC capability response message shall be sent by the BTU-R only after reception of evConfigSw. + +**Table 20/G.998.3 – FEC capability request** + +| Octet # | Content | Data type | Description | +|---------|----------------------------------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| 1 | MsgID = 11 | Message ID | | +| 2.6-7 | Request | Enumerated (enum) (0-2) | 0 – Request FEC Capability report
1 – Disable FEC (BTU-C only)
2 – Enable FEC (BTU-C only) | +| 2.3-5 | Reserved | | | +| 2.0-2 | Redundancy word size (2, 4, 8, 16, 20) | enum (1-4) | FEC redundancy word size ( $2^k$ for $k = 1..4$ , 20 for $k = 5$ ). If Request value is 0 or 1 (Request/Disable) the value is ignored. | +| 3 | Code word size (in octets) | enum (20-255) | FEC code word size. If request value is 0 or 1 (Request/Disable) the value is ignored. | +| 4.6-7 | Reserved | | | +| 4.3-5 | Interleaver param B | enum (0-5) | Interleaver param B.
The interleaver depth = $3^A * 2^B$ .
If request value is 0 or 1 (Request/Disable) the value is ignored. | +| 4.2 | Interleaver param A | enum (0-1) | Interleaver param A. If request value is 0 or 1 (Request/Disable) the value is ignored. | +| 4.0-1 | Interleaver type | enum (0-2) | 0 – No interleaver
1 – Block interleaver
2 – Convolution interleaver | + +#### 13.3.4.13 FEC capability response + +The FEC capability response message is sent in response to a FEC capability request message (message ID 11). It reports FEC and interleaver parameters for the source BTU. + +**Table 21/G.998.3 – FEC capability response** + +| Octet # | Content | Data type | Description | +|---------|----------------------------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | MsgID = 12 | Message ID | | +| 2.7 | Response | enum (0-1) | 0 – OK
1 – UTC (Unable to comply) | +| 2.3-6 | Reserved | | | +| 2.0-2 | Redundancy word size (2, 4, 8, 16, 20) | enum (1-4) | Current/Maximum supported redundancy word size ( $2^k$ for $k = 1..4$ , 20 for $k = 5$ ). If FEC is not supported the value shall be 0. When FEC is disabled, maximum possible value is returned on request. When FEC is enabled, current value is returned on request. | +| 3 | Code word size (in octets) | enum (20-255) | Current/Maximum supported FEC code word size. If FEC is not supported the value shall be 0. When FEC is disabled, maximum possible value is returned on request. When FEC is enabled, current value is returned on request. | +| 4.6-7 | Reserved | | | +| 4.3-5 | Interleaver param B | enum (0-5) | Current/Maximum supported interleaver param B.
The interleaver depth = $3^A \times 2^B$ .
If interleaver is not supported, the value shall be 0. When interleaver is disabled, maximum possible value is returned on request. When interleaver is enabled, current value is returned on request. | +| 4.2 | Interleaver param A | enum (0-1) | Current/Maximum supported interleaver param A. If interleaver is not supported, the value shall be 0. When interleaver is disabled, maximum possible value is returned on request. When interleaver is enabled, current value is returned on request. | +| 4.0-1 | Interleaver type | enum (0-3) | 00 – None supported
01 – Block interleaver supported
10 – Convolution interleaver supported
11 – Both types supported | + +If BTU-R does not support FEC, it shall respond with UTC value in response field on FEC request from BTU-C to enable FEC. When FEC is disabled, maximum possible values for all parameters shall be returned in response to FEC request message. Current values for all parameters shall be returned in response to FEC request to enable FEC, after they have been set to the requested values by evConfigSw event. + +#### 13.3.4.14 Pair mapping request + +The pair mapping request message is used to determine the mapping between the physical pair (or loop) number labelled on the equipment and the logical wire pair (or loop) ordinal number. While this mapping is vendor specific, this information is useful for troubleshooting circuits. The response to this request shall be message ID 14. + +**Table 22/G.998.3 – Pair mapping request** + +| Octet # | Content | Data type | Description | +|---------|------------|------------|-------------| +| 1 | MsgID = 13 | Message ID | | +| 2-4 | Reserved | | | + +#### **13.3.4.15 Pair mapping response** + +The pair mapping response message is sent in response to a mapping request message (message ID 13). It is used to determine the mapping between the physical pair (or loop) number and the logical wire pair (or loop) ordinal number. The physical pair number is the number labelled externally on the equipment. The physical pair number is composed of two octets, with the first octet containing the most significant byte, and the second octet containing the least significant byte. For example, if the 16-bit number in octets 3/4 contains the value 4, then the logical wire pair 1 in the current group is transported over the equipment's physical pair labelled number 4. + +**Table 23/G.998.3 – Pair mapping response** + +| Octet # | Content | Data type | Description | +|----------------------------------------|------------------------|----------------|--------------------------------------------------------------------------------------------| +| 1 | MsgID = 14 | Message ID | | +| 2 | Number of pairs = M | uint 8 (1..32) | Number of wire pairs in the aggregation group | +| 3,4 | Physical pair number 1 | uint 16 | Physical number of the pair corresponding to the 1st logical pair in the aggregation group | +| 5,6 | Physical pair number 2 | uint 16 | Physical number of the pair corresponding to the 2nd logical pair in the aggregation group | +| . | . | | | +| . | . | | | +| . | . | | | +| $2 \times M + 1$ ,
$2 \times M + 2$ | Physical pair number M | uint 16 | Physical number of the pair corresponding to the Mth logical pair in the aggregation group | + +#### **13.3.4.16 Reserved** + +The message IDs 15-127 are reserved. + +#### **13.3.4.17 Vendor-specific messages** + +The message IDs 128-255 are reserved for vendor-specific (proprietary) messages. + +# **14 Handshaking** + +## **14.1 Overview** + +All of the bonding system pairs (modems) shall use G.Handshake as defined in ITU-T Rec. G.994.1 for startup and choose Synchronous Transfer Mode (STM) mode for each of the pairs. G.Handshake negotiation and modem parameter selection shall be done per modem technology. + +The Institute of Electrical and Electronics Engineers (IEEE) 802.3ah standard defines procedure for Pair Discovery. The same discovery shall be used in TDiM bonding, using Physical Medium Independent (PMI) discovery codepoints defined in ITU-T Rec. G.994.1. + +## 14.2 Bonding Npar(2) codepoint + +ITU-T Rec. G.994.1 defines bonding Npar(2) coding in the identification field (Table 9.37). The TDIM system shall set the "TDIM bonding" bit to one in the CLR/CL handshake messages on all modems. + +## 14.3 Pair discovery + +IEEE 802.3ah defines process and handshake transactions for pair discovery, see 61.2.2.8.3, 61.3.12.1, 61.A2. A TDIM system shall use the same pair discovery process and transactions to identify far end modems, which belong to the same aggregation group, by incorporating IEEE 802.3ah standard by reference. + +The use of handshake transactions for pair discovery provides means for detecting inconsistencies without a need for a full wakeup of the system. However, once the system has initiated, the pair mapping messages (see 13.3.4.14, 13.3.4.15) shall be used and shall take precedence over the handshake pair discovery. + +# 15 Performance monitoring + +The following PM counters are used in order to monitor the performance of the aggregation group: + +**Table 24/G.998.3 – Performance monitoring counters** + +| PM register | Data type | Description | +|---------------------|-----------|----------------------------------------------------------------------------------------------------------------------------------| +| CRC-4 anomaly count | uint 16 | Frame errors. Sum of CRC-4 errors on all pairs in the aggregation group, simultaneous errors on m lines shall be counted m times | +| CRC-6 anomaly count | uint 16 | Super-frame errors. Sum of all pairs in the aggregation group | +| CRC-8 anomaly count | uint 16 | Number of corrupted events/Messages, sum of all pairs in the aggregation group | + +All the PM counters are "Cleared on Read" and are "stuck" when reaching maximum value (65535). + +# Annex A + +## Modem rate matching + +## A.1 Introduction + +This annex provides implementation details for the modem rate matching block, which allows bonding over pairs (modems) that are not synchronized to the aggregation time domain. + +The purpose of this annex is to provide a solution for multi loop bonding with pairs with rate that deviates from the nominal $n \times 8$ kbit/s. This deviation can be derived by either of the following two causes: + +- 1) The DSL pair is asynchronous to the aggregation time domain. +- 2) The DSL pair nominal frequency is different from the $n \times 8$ kbit/s nominal rate, since the DSL technology does not guarantee integer multiples of 8 kbit/s (e.g., ADSL2). + +With modem rate matching, Figures 1 and 6 in the main body of the Recommendation shall be as in Figures A.1 and A.2, respectively. + + + +The diagram illustrates the data flow model. At the top, three input streams are shown: 'ATM cells', 'TDM PCM stream', and 'Ethernet packets'. These inputs enter a trapezoidal block labeled 'Service encapsulation'. Below this block is a rectangular block labeled 'FEC interleaver (optional)'. This is followed by another trapezoidal block labeled 'Aggregation'. From the 'Aggregation' block, three parallel vertical lines lead to three identical rectangular blocks. Each block is divided into two sections: 'Modem rate match.' on top and 'Modem' on the bottom. A dashed line is shown between the second and third 'Modem' blocks. To the right of the third 'Modem' block, the text 'Single-pair modems / PMDs' is present. + +Data flow model diagram showing the flow from TDM PCM stream, ATM cells, and Ethernet packets through Service encapsulation, FEC interleaver (optional), Aggregation, and finally to multiple Modem rate match and Modem units. + +G.998.3\_FA.1 + +Figure A.1/G.998.3 – Modified Figure 1 – Data flow model + + + +Figure A.2/G.998.3 – Modified Figure 6 – Clock synchronization reference model. The diagram illustrates the flow of data from various services through a series of processing stages to multiple modems. At the top, 'Asynchronous services (e.g., ATM, Ethernet)' enter an 'Encapsulation' block. 'Synchronous services (TDM)' enter 'Stuffing' blocks, which also receive 'Clk' and 'Data' inputs. The outputs of 'Encapsulation' and 'Stuffing' blocks enter a 'Service Mux'. A red dashed line labeled 'Service time domain' is positioned above the 'Service Mux'. The output of the 'Service Mux' enters an 'FEC interleaver (optional)'. A red dashed line labeled 'Aggregation time domain' is positioned below the 'FEC interleaver'. The output of the 'FEC interleaver' enters an 'Aggregation' block. An 'Aggregation ref. clock' is shown entering the 'Aggregation' block from the right. The output of the 'Aggregation' block enters multiple 'Modem rate match.' blocks, which in turn enter 'Modem' blocks. A red dashed line labeled 'Modems time domain' is positioned below the 'Modem' blocks. The diagram is labeled 'G.998.3\_FA.2' at the bottom right. + +**Figure A.2/G.998.3 – Modified Figure 6 – Clock synchronization reference model** + +ADSL2 rate cannot be predetermined to provide a fixed rate which is a multiple of 8 kbit/s. The rate may exceed the desired target by up to 8 kbit/s. To allow such operation, modem rate matching shall provide a mechanism to add up to 8 kbit/s. + +Additional adaptation of $\pm 8$ kbit/s is provided to overcome frequency deviation (due to the DSL link being derived from a clock which is asynchronous to the aggregation time domain). $\pm 8$ kbit/s can compensate for frequency deviation of above 70 ppm in case of 55.2 Mbit/s pair (VDSL). Thus, the modem rate matching is defined to compensate for a total deviation of $-8$ kbit/s to $+16$ kbit/s. + +## A.2 Work principles + +- The modem rate matching mechanism is enabled/disabled for all the aggregation group, and not per specific pairs. +- Modem rate matching overhead occupies 8 kbit/s on each pair. +- Modem payload size granularity is in bytes. +- Modem payload size can change every bonding sub-block (1 ms). +- Modem payload size change can be done per pair. +- The BTU-R conveys its capabilities over the frame header bits In6[4:3], and the BTU-C determines the operation mode over those bits. +- The modem rate matching can compensate for total deviation of $-8$ kbit/s to $+16$ kbit/s. + +## A.3 Coordination between BTU-C and BTU-R + +The use of the modem rate matching is determined by the BTU-C. The BTU-R conveys its capabilities over the Frame header bits In6[4:3], and the BTU-C responds with the required operation mode. Both ends shall operate in the same mode. + +Table A.1 summarizes the possible options for each BTU: + +**Table A.1/G.998.3 – Modem rate matching coordination between BTU-C and BTU-R** + +| In6[4] | In6[3] | Transmitting entity | | +|--------|--------|---------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| +| | | BTU-R | BTU-C | +| 0 | 1 | Only modem rate matching is supported. In this case, both ends shall support it to perform the bonding. | Set the operation mode of both ends to modem rate matching enabled. | +| 1 | 0 | Modem rate matching is not supported. In this case, both ends shall operate without it. | Set the operation mode of both ends to modem rate matching disabled. | +| 1 | 1 | Modem rate matching can be enabled or disabled. | N/A | + +## A.4 Framing format + +Modem rate matching occupies an additional overhead of 8 kbit/s per DSL pair. This overhead is not consumed if modem rate matching is disabled. + +If modem rate matching is enabled, the overhead byte (RM-byte) is added every mini-frame (1 ms), following the frame header field. + + + +The diagram illustrates the framing format for a 1 ms mini-frame. It shows a sequence of bytes, with the first byte being the 'Frame overhead byte' and the second byte being the 'RM overhead byte'. A detailed view of the RM overhead byte shows its bit structure: + +| | | | | | +|---|---|------|-----|-----| +| R | R | N2mF | NmF | CmF | +| M | E | 1 | 0 | 1 | +| 1 | S | 1 | 0 | 1 | + +The diagram also indicates a 'Bonding sub-block' of 125 μs duration within the 1 ms mini-frame. The label 'G.998.3\_FA.3' is present in the bottom right corner. + +Diagram of frame format showing a 1 ms mini-frame containing a frame overhead byte and an RM overhead byte, with a detailed view of the RM overhead byte structure. + +**Figure A.3/G.998.3 – Multi-pair synchronization – Frame format with modem rate matching** + +The fields in the RM overhead byte are defined in Table A.2: + +**Table A.2/G.998.3 – Fields in the RM overhead byte** + +| Field | Bits | Description | +|-------|------|--------------------------------------------------------------------------| +| RMI | 7 | Modem rate matching overhead indication – set to '0' | +| RES | 6 | Reserved for future use – set to '1' | +| N2mF | 5:4 | The operation to be performed 2 mini-frames from the current mini-frame. | +| NmF | 3:2 | The operation to be performed in the next mini-frame. | +| CmF | 1:0 | The operation to be performed in the current mini-frame. | + +Table A.3 defines the values used in fields N2mF, NmF and CmF. + +**Table A.3/G.998.3 – Values in fields N2mF, NmF and CmF** + +| Value | Description | +|-------|----------------------------------------------------------------------| +| 00 | A byte shall be omitted at the end of the relevant mini-frame. | +| 01 | No change to the nominal number of bytes of the relevant mini-frame. | +| 10 | A byte shall be added at the end of the relevant mini-frame. | +| 11 | 2 bytes shall be added at the end of the relevant mini-frame. | + +The BTU-C and the BTU-R coordinate the modem rate matching mode of operation as described in clause A.3. If modem rate matching is enabled, the byte following the frame header overhead byte shall be an RM overhead byte, its MSB being thus set to '0' (while the payload data is set to 0xE2 during the synchronization phase). + +## A.5 Modem rate matching operation + +In each mini-frame the modem rate matching mechanism either omits a byte, adds a byte, adds 2 bytes, or transfers the nominal number of bytes unchanged. The byte is added/omitted to/from the last bonding sub-block of the mini-frame. + +For each mini-frame, the values used in fields N2mF, NmF and CmF, that determine the required operation, are conveyed 3 times: The value in field N2mF indicates the operation to be performed 2 mini-frames from the current mini-frame, the value in field NmF indicates the operation to be performed in the next mini-frame, the value in field CmF indicates the operation to be performed in the current mini-frame. The receiver uses a "majority vote" to decide on the required operation. Thus a single error which effects one of the fields can be corrected. + +# Appendix I + +## Clock synchronization examples + +The following text and figures are informative. Figure I.1 elaborates the clock synchronization mechanism in more details. + + + +The diagram illustrates the clock synchronization architecture across three time domains separated by vertical dashed red lines: + +- Services time domain:** On the left, multiple input streams are shown: Plesiochronous TDM 1 through n, and Asynchronous (ATM, Ethernet, etc.). The TDM streams pass through 'Stuff.' blocks and then into a 'Service Mux' (Tx). The asynchronous streams also enter the 'Service Mux' (Tx). The 'Service Mux' (Tx) output goes to the 'Aggregation' (Tx) block. +- Aggregation time domain:** This central domain contains 'Aggregation' (Tx) and 'Aggregation' (Rx) blocks. An 'External Reference clock' is input to 'Mux 1', which also receives input from a 'free-run clock oscillator'. The output of 'Mux 1' is fed into the 'Aggregation' (Tx) block. The 'Aggregation' (Tx) block output goes to the 'Modem time domain'. +- Modem time domain:** On the right, there are three 'Modem rate match.' blocks, each connected to a 'Modem' block. The 'Aggregation' (Tx) output is distributed to these 'Modem rate match.' blocks. Each 'Modem rate match.' block also receives a clock signal from 'Mux 2'. 'Mux 2' receives input from the 'Aggregation' (Rx) block and a 'free-run clock oscillator'. The 'Modem' blocks output back to the 'Modem rate match.' blocks, which then feed into the 'Aggregation' (Rx) block. The 'Aggregation' (Rx) block output goes to the 'Service Mux' (Rx). The 'Service Mux' (Rx) output is then distributed: one path goes through 'de-stuff.' blocks to the Plesiochronous TDM 1 through n outputs, and another path goes directly to the Asynchronous (ATM, Ethernet, etc.) output. + +Labels G.998.3\_F1.1 are present in the bottom right corner of the diagram area. + +Diagram of clock synchronization mechanisms in a TDM bonding system, showing Services, Aggregation, and Modem time domains. + +Figure I.1/G.998.3 – Peer time domains and clock synchronization + +## I.1 Clock domains + +There are 3 clock domains in a TDM bonding system: + +- **Services clock domain:** with the original clock of each TDM plesiochronous service. Each clock should comply with the TDM service clock requirements (e.g., 32 PPM for T1, 20 PPM for T3). +- **Aggregation time domain:** can be derived from the external reference clock or from an internal free-run clock (by Mux 1). +- **Modem time domain:** DSL modems may work with two clock modes: Synchronous and Plesiochronous. The clock can be derived from an internal free-run clock or from the aggregation time domain (by Mux 2). In synchronous mode, all modems use the modem data rate clock as reference for their line symbol rate. In plesiochronous mode, each modem + +can use a free-run clock as reference for its line symbol rate. Modem rate matching is required in plesiochronous mode. Modem rate matching can be done internally in the modem for DSL technologies that support it (e.g., SHDSL) or as part of the bonding system, externally to the modem, for DSL technologies that work only in synchronous mode (e.g., ADSL2). + +## I.2 Rate adaptation between clock domains + +### I.2.1 Between services time domain and aggregation time domain + +Rate adaptation between services time domain and aggregation time domain is **always implemented**. + +Rate adaptation is not required for asynchronous services such as Ethernet or ATM. + +Rate adaptation is required for TDM plesiochronous services. It is achieved by the stuffing mechanism explained in [10.4 TDM service stuffing]. The stuffing mechanism adapts the data rate of the each TDM service to the data rate of the aggregation time domain. The peer system at the FE de-stuffs the data and restores the original TDM service clock. + +### I.2.2 Between aggregation time domain and modem time domain + +Rate adaptation between aggregation time domain and modem time domain is **optional**. + +In case that the DSL modems support plesiochronous mode (such as G.991.2), rate adaptation is performed by the modems with their stuffing capability. In case that the DSL modems support only synchronous mode (such as ADSL2) rate adaptation between aggregation time domain and modem time domain is done in the modem rate matching block (see Figure I.2.) + +## I.3 Timing operation modes + +A bonding system may choose to work with loop timing or with through timing as seen in Figure I.2. + + + +The diagram illustrates two timing operation modes for a bonding system consisting of a BTU-C (Bonding Terminal Unit - Client) and a BTU-R (Bonding Terminal Unit - Remote). + +**Loop timing:** In this mode, the BTU-C and BTU-R are connected via a dashed line representing the aggregation time domain. The BTU-C has a solid line representing the modem time domain. The BTU-R has a solid line representing the modem time domain. The BTU-R is shown with a callout bubble stating "BTU-R should work with loop timing as well". + +**Pass through timing:** In this mode, the BTU-C and BTU-R are connected via a dashed line representing the aggregation time domain. The BTU-C has a solid line representing the modem time domain. The BTU-R has a solid line representing the modem time domain. The BTU-R is shown with a callout bubble stating "BTU-R may work with internal clock". + +The diagram also shows "Services" entering and leaving the BTU-C and BTU-R units. The BTU-C is on the left and the BTU-R is on the right. The aggregation time domain is represented by a dashed line between them. The modem time domain is represented by a solid line. The BTU-R callout bubbles are at the bottom right of each section. + +G.998.3\_F1.2 + +Diagram illustrating Loop timing and Pass through timing modes for BTU-C and BTU-R units. + +Figure I.2/G.998.3 – Loop timing and through timing + +## I.4 Examples + +### I.4.1 Plesiochronous services, external reference clock, loop timing and plesiochronous DSL modems + +In Figure I.3, modem rate matching is part of the plesiochronous DSL modems. + + + +The diagram illustrates the architecture of plesiochronous services with an external reference clock, divided into three main time domains separated by vertical dashed red lines: + +- Services time domain:** On the left, multiple input signals are shown: Plesiochronous TDM 1, Plesiochronous TDM n, and Asynchronous (ATM, Ethernet, etc.). These enter a 'Stuff.' block. An 'External Reference clock' is also input to this domain. The output of the 'Stuff.' block goes to a 'Service Mux' block. +- Aggregation time domain:** The 'Service Mux' block contains a 'Tx' (transmitter) and an 'Rx' (receiver). The 'Tx' output goes to an 'Aggregation' block, which also contains a 'Tx'. The 'Aggregation Tx' output goes to the 'Modem time domain'. The 'Aggregation Rx' output goes to the 'Service Mux' block. A 'Loop timing at the bonding level' is indicated between the Aggregation and Modem domains. +- Modem time domain:** On the right, there are three parallel paths. Each path consists of a 'Modem rate match.' block followed by a 'Modem' block. The 'Modem rate match.' blocks receive data from the 'Aggregation Tx'. The 'Modem' blocks are connected to a 'free-run clock oscillator'. A feedback loop is shown from the 'Modem' blocks back to the 'Aggregation Rx' block. + +The diagram is labeled 'G.998.3\_F1.3' at the bottom right. + +Diagram of plesiochronous services with external reference clock, showing Services time domain, Aggregation time domain, and Modem time domain. + +Figure I.3/G.998.3 – Example of plesiochronous services with external reference clock + +#### I.4.2 Plesiochronous services, no external reference clock, loop timing and synchronous DSL modems + +In Figure I.4, modem rate matching is part of the bonding system, external to the synchronous DSL modems. + + + +The diagram illustrates the architecture for plesiochronous services without an external reference clock, divided into three time domains by vertical dashed red lines: + +- Services time domain:** On the left, inputs include Plesiochronous TDM 1 through n, and Asynchronous (ATM, Ethernet, etc.). In the transmit (Tx) path, TDM signals pass through 'Stuff.' blocks into a 'Service Mux'. In the receive (Rx) path, signals from the 'Service Mux' pass through 'de-stuff.' blocks to produce the output TDM signals. +- Aggregation time domain:** The 'Service Mux Tx' output goes to an 'Aggregation Tx' block. The 'Aggregation Rx' block output goes to a 'Service Mux Rx' block. A 'free-run clock Oscillator' is connected to both the Aggregation Tx and Rx blocks. A label 'Loop timing at the bonding level' points to the Aggregation Rx block. +- Modem time domain:** The 'Aggregation Tx' block connects to three 'Modem rate match.' blocks, which in turn connect to three 'Modem' blocks. The 'Modem' blocks connect to the 'Aggregation Rx' block via their 'Modem rate match.' blocks. Each 'Modem' block has its own 'free-run clock Oscillator'. + +The diagram is labeled 'G.998.3\_F1.4' in the bottom right corner. + +Diagram of plesiochronous services with no external reference clock, showing transmission and reception paths across three time domains: Services, Aggregation, and Modem. + +Figure I.4/G.998.3 – Example of plesiochronous services, no external reference clock, loop timing and synchronous DSL modems + +#### I.4.3 Plesiochronous services, external reference clock, through timing and plesiochronous DSL modems + +In Figure I.5, modem rate matching is part of the plesiochronous DSL modems. + + + +The diagram illustrates the architecture for plesiochronous services using an external reference clock. It is divided into three main time domains by vertical dashed red lines: **Services time domain** (left), **Aggregation time domain** (center), and **Modem time domain** (right). + +**Transmitter (Tx) Path:** In the Services time domain, multiple inputs are shown: Plesiochronous TDM 1, Plesiochronous TDM n, and Asynchronous (ATM, Ethernet, etc.). The TDM signals pass through 'Stuff.' blocks and then into a 'Service Mux'. The Asynchronous signals also enter the 'Service Mux'. An 'External Reference clock' is fed into the 'Service Mux Tx'. The output of the 'Service Mux Tx' goes to an 'Aggregation Tx' block in the Aggregation time domain. The output of the 'Aggregation Tx' is distributed to three 'Modem rate match.' blocks in the Modem time domain. Each 'Modem rate match.' block is connected to a 'Modem' block. A 'free-run clock oscillator' is connected to the middle 'Modem' block. Arrows indicate data flow from left to right. + +**Receiver (Rx) Path:** The 'Modem' blocks in the Modem time domain send data to 'Modem rate match.' blocks, which then connect to an 'Aggregation Rx' block in the Aggregation time domain. The output of the 'Aggregation Rx' goes to a 'Service Mux Rx' block. The 'Service Mux Rx' outputs are then processed: one path goes through 'de-stuff.' blocks to produce Plesiochronous TDM 1 and Plesiochronous TDM n; another path outputs Asynchronous (ATM, Ethernet, etc.) data. Arrows indicate data flow from right to left. + +Labels G.998.3\_F1.5 are present at the bottom right of the diagram. + +Diagram of plesiochronous services with external reference clock and DSL modems. + +**Figure I.5/G.998.3 – Example of plesiochronous services, external reference clock, through timing and plesiochronous DSL modems** + +#### I.4.4 Plesiochronous services, no external reference clock, through timing and synchronous DSL modems + +In Figure I.6, modem rate matching is not required, since the DSL modems are synchronous to the aggregation layer rate allocation and to the aggregation time domain. This example is applicable for SHDSL modems and not to ADSL2 modems. + + + +Figure I.6/G.998.3 – Example of plesiochronous services, no external reference clock, through timing and synchronous DSL modems. The diagram shows a 'Services time domain' on the left and an 'Aggregation and modem time domain' on the right, separated by a dashed red line. In the transmit (Tx) path, multiple 'Plesiochronous TDM' inputs (1 to n) pass through 'Stuff.' blocks and then into a 'Service Mux'. Asynchronous data (ATM, Ethernet, etc.) also enters the 'Service Mux'. The output of the 'Service Mux' goes to an 'Aggregation' block. A 'free-run clock oscillator' provides a clock signal to the 'Aggregation' block and to a series of 'Modem' blocks. The 'Aggregation' block outputs to the 'Modem' blocks. In the receive (Rx) path, data from the 'Modem' blocks goes to an 'Aggregation' block, which then outputs to a 'Service Mux'. The 'Service Mux' outputs to 'de-stuff.' blocks, which then output to the 'Plesiochronous TDM' outputs (1 to n). Asynchronous data (ATM, Ethernet, etc.) is also shown as an output from the 'Service Mux'. + +**Figure I.6/G.998.3 – Example of plesiochronous services, no external reference clock, through timing and synchronous DSL modems** + +# Appendix II + +## Management objects + +This appendix provides the layer management specification for M2DSL TDIM functionality of devices implementing this Recommendation. It includes aggregation group provisioning, service provisioning, FEC/interleaving provisioning, group performance and pair status. + +### a) *Management model and containment* + +#### i) **Managed objects** + +The following objects provide management functionality for the TDIM protocol: + +**oGroup** This managed object class provides the management controls necessary to allow an instance of a bonded group to be managed. + +**oService** This managed object class provides the management controls necessary to allow an instance of a service in the bonded group to be managed. + +**oPair** This managed object class provides the management controls necessary to allow an instance of a pair to be managed. + +#### **ii) Capabilities** + +This Recommendation makes use of the concept of *packages* as defined in ISO/IEC 10165-4:1992 as a means of grouping behaviour, attributes, actions, and notifications within a managed object class definition. Packages may either be mandatory, or conditional, that is to say, present if a given condition is true. Within this Recommendation, *capabilities* are defined, each of which corresponds to a set of packages, which are components of a number of managed object class definitions and which share the same condition for presence. Implementation of the appropriate basic and mandatory packages is the minimum requirement for claiming conformance to G.998.3 TDM management. Implementation of an entire optional capability is required in order to claim conformance to that capability. The capabilities and packages for G.998.3 TDM management are specified in Table II.1: + +**Table II.1/G.998.3 – TDM management capabilities** + +| | | | TDM bonding capability (Mandatory) | FEC capability (Optional) | +|--------------------------------------|-----------|---------|------------------------------------|---------------------------| +| oGroup managed object class | | | | | +| aGroupID | ATTRIBUTE | GET | x | | +| aGroupEnd | ATTRIBUTE | GET | x | | +| aGroupStatus | ATTRIBUTE | GET | x | | +| aGroupCapacity | ATTRIBUTE | GET | x | | +| aGroupRate | ATTRIBUTE | GET | x | | +| aCRC4Errors | ATTRIBUTE | GET | x | | +| aCRC6Errors | ATTRIBUTE | GET | x | | +| aCRC8Errors | ATTRIBUTE | GET | x | | +| aFECSupported | ATTRIBUTE | GET | x | | +| aFECAdminState | ATTRIBUTE | GET-SET | | x | +| aFECWordSize | ATTRIBUTE | GET-SET | | x | +| aFECRedundancySize | ATTRIBUTE | GET-SET | | x | +| aFECInterleaverType | ATTRIBUTE | GET-SET | | x | +| aFECInterleaverDepth | ATTRIBUTE | GET-SET | | x | +| oService managed object class | | | | | +| aServiceID | ATTRIBUTE | GET | x | | +| aServiceType | ATTRIBUTE | GET-SET | x | | +| aServiceSize | ATTRIBUTE | GET-SET | x | | +| oPair managed object class | | | | | +| aPairID | ATTRIBUTE | GET | x | | +| aPairStatus | ATTRIBUTE | GET | x | | +| aPairPhysicalID | ATTRIBUTE | GET | x | | +| aPairRemotePhysicalID | ATTRIBUTE | GET | x | | + +b) *oGroup managed object class* + +i) **aGroupID** + +ATTRIBUTE + +SYNTAX: + +INTEGER + +DESCRIPTION: + +A read-only value to uniquely identify a bonding group. + +ii) **aGroupEnd** + +ATTRIBUTE + +SYNTAX: + +ENUM {subscriber, office} + +DESCRIPTION: + +A read-only value to uniquely identify a sub-type of the BTU. The value of subscriber indicates that the BTU operates as BTU-R, the value of office indicates that the BTU operates as BTU-C. + +iii) **aGroupStatus** + +ATTRIBUTE + +SYNTAX: + +ENUM {Down, Init, Up} + +DESCRIPTION: + +A read-only value indicating current operation status of a bonding group. + +iv) **aGroupCapacity** + +ATTRIBUTE + +SYNTAX: + +INTEGER {1-32} + +DESCRIPTION: + +A read-only value to specifying a maximum number of PAIRs (modems) which can be grouped in the group identified by aGroupID. + +v) **aGroupRate** + +ATTRIBUTE + +SYNTAX: + +INTEGER + +DESCRIPTION: + +A read-only value indicating current net data rate of a bonding group. A zero value is returned if aGroupStatus is "Down" or "Init". + +#### vi) **aFECSupported** + +ATTRIBUTE + +SYNTAX: + +BOOLEAN + +DESCRIPTION: + +A read-only value indicating if the optional Forward Error Correction (FEC) functionality is supported. A BTU that can perform FEC shall return the value of "true". Otherwise a "false" value shall be returned. + +#### vii) **aCRC4Errors** + +ATTRIBUTE + +SYNTAX: + +Generalized non-resettable counter. + +DESCRIPTION: + +The total number of CRC-4 errors (frame header error) on all pairs in the aggregation group, simultaneous errors on M lines shall be counted M times. + +#### viii) **aCRC6Errors** + +ATTRIBUTE + +SYNTAX: + +Generalized non-resettable counter. + +DESCRIPTION: + +The total number of CRC-6 errors (super-frame error) of all pairs in the aggregation group, simultaneous errors on M pairs shall be counted 1 time. + +#### ix) **aCRC8Errors** + +ATTRIBUTE + +SYNTAX: + +Generalized non-resettable counter. + +DESCRIPTION: + +The total number of CRC-8 errors (event/message error) of all pairs in the aggregation Group, simultaneous errors on M lines shall be counted M times. + +#### x) **aFECAdminState** + +ATTRIBUTE + +SYNTAX: + +ENUM { Enabled, Disabled } + +DESCRIPTION: + +A read-write value that indicates the state of the optional FEC function per aggregation group. + +A GET operation returns the current state of the FEC function. + +A SET operation, allowed on BTU-C only, changes the state of FEC function to the indicated value only if aFECSupported is true and the link is down. If aFECSupported is false or the link is not down, the operation has no effect. + +#### **xi) aFECWordSize** + +ATTRIBUTE + +SYNTAX: + +INTEGER {20-255} + +DESCRIPTION: + +A read-write value specifying FEC code word size in octets. + +A GET operation returns the current value of FEC code word size if aFECAdminState is enabled. Otherwise a maximum supported FEC code word size value is returned. + +SET operation, allowed on BTU-C only, changes the FEC code word size to the indicated value only if aFECSupported is true, the link is down. If aFECSupported is false or the link is not down, the operation has no effect. + +#### **xii) aFECRedundancySize** + +ATTRIBUTE + +SYNTAX: + +INTEGER {2, 4, 8, 16, 20} + +DESCRIPTION: + +A read-write value specifying FEC redundancy word size in octets. + +A GET operation returns the current value of FEC redundancy word size if aFECAdminState is enabled. Otherwise a maximum supported FEC Redundancy word size value is returned. + +SET operation, allowed on BTU-C only, changes the FEC redundancy word size to the indicated value only if aFECSupported is true, the link is down. If aFECSupported is false or the link is not down, the operation has no effect. + +#### **xiii) aFECInterleaverType** + +ATTRIBUTE + +SYNTAX: + +ENUM { + None, + Block, + Convolution +} + +DESCRIPTION: + +A read-write value specifying the type of interleaver. + +A GET operation returns the current value of interleaver type if aFECAdminState is enabled. Otherwise a bitmask consisting of maximum supported types is returned (e.g., "None", "Block", "Convolution" or "Block"&"Convolution"). + +A SET operation, allowed on BTU-C only, changes the interleaver type to the indicated value only if aFECSupported is true and the link is down. If aFECSupported is false or the link is not down, the operation has no effect. + +#### xiv) **aFECInterleaverDepth** + +ATTRIBUTE + +SYNTAX: + +INTEGER {1, 2, 3, 4, 6, 8, 12, 16, 24, 32, 48, 96} + +DESCRIPTION: + +A read-write value specifying interleaver depth. + +A GET operation returns the current value of interleaver depth if aFECAdminState is enabled. Otherwise a maximum supported depth value is returned. + +SET operation, allowed on BTU-C only, changes the interleaver depth to the indicated value only if aFECSupported is true, the link is down. If aFECSupported is false or the link is not down, the operation has no effect. + +### c) *oServices managed object calss* + +#### i) **aServiceID** + +ATTRIBUTE + +SYNTAX: + +INTEGER {1-60} + +DESCRIPTION: + +A read-only value to uniquely identify a service. There can be up to 60 services defined over TDM bonded facility. Services with lower IDs have higher priority in case of bandwidth degradation. + +#### ii) **aServiceType** + +ATTRIBUTE + +SYNTAX: + +ENUM {DS1, E1, NxDS0, NxE0, DS3, E3, Clock, Ethernet, ATM, GFPnoFCS, GFP} + +DESCRIPTION: + +A read-write value specifying the service type of the BTU. + +A GET operation returns currently assigned value for a specific service identified by aServiceID. + +A SET operation, allowed on BTU-C only, changes the service type to the indicated value if the link is down. If the link is not down, the operation has no effect. + +#### iii) **aServiceSize** + +ATTRIBUTE + +SYNTAX: + +INTEGER + +DESCRIPTION: + +A read-write value specifying the number of bytes per bonding sub-block for a specific service identified by aServiceID (number of channels for fractional DS1/E1 + +(NxDS0/NxE0) or maximal number of bytes for asynchronous services (Ethernet, ATM, GFPnoFCS and GFP)). + +A GET operation returns current value. + +A SET operation, allowed on BTU-C only, changes the service size to the indicated value if the link is down. If the link is not down or the service type is fixed rate TDM service (aServiceType is DS1, E1, DS3, E3 or Clock), the operation has no effect. + +### d) *oPair managed object class* + +#### i) **aPairID** + +ATTRIBUTE + +SYNTAX: + +INTEGER {1-32} + +DESCRIPTION: + +A read-only value to uniquely identify a wire pair (modem) in the bonding group, i.e., logical number of the pair in the aggregation group. This value is never greater than aGroupCapacity. + +#### ii) **aPairStatus** + +ATTRIBUTE + +SYNTAX: + +ENUM {Down, Handshake, Activation, Synching, Synched, Adding, InGroup, SyncLost, Removing} + +DESCRIPTION: + +A read-only value indicating current pair status. All the states are defined in 12.1 (Pair management and control). + +#### iii) **aPairPhysicalID** + +ATTRIBUTE + +SYNTAX: + +INTEGER + +DESCRIPTION: + +A read-only value indicating physical number of the pair (labelled externally on the equipment). + +#### iv) **aPairRemotePhysicalID** + +ATTRIBUTE + +SYNTAX: + +INTEGER + +DESCRIPTION: + +A read-only value indicating physical number of the remote pair (labelled externally on the equipment) connected to the local pair specified by aPairID. + + + +# 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/original/G/T-REC-G.102-198811-I_PDF-E.pdf b/original/G/T-REC-G.102-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..1964989f125d727b78d67b8973d64708ce381987 Binary files /dev/null and b/original/G/T-REC-G.102-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.172-198811-I_PDF-E.pdf b/original/G/T-REC-G.172-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..065bab85fe4b1242455db4b8efcd208ba4feac6f Binary files /dev/null and b/original/G/T-REC-G.172-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.181-199303-I_PDF-E.pdf b/original/G/T-REC-G.181-199303-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..dfc8a6195a49d85210beaef11863860d5bf0502f Binary files /dev/null and b/original/G/T-REC-G.181-199303-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.213-198811-I_PDF-E.pdf b/original/G/T-REC-G.213-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..b7c0cbb25d0e9e851e0a2fac87640e6f1567caa0 Binary files /dev/null and b/original/G/T-REC-G.213-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.215-198811-I_PDF-E.pdf b/original/G/T-REC-G.215-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..e493fa424de61ef47dd93bffe3a24290331f8cfc Binary files /dev/null and b/original/G/T-REC-G.215-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.225-198811-I_PDF-E.pdf b/original/G/T-REC-G.225-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..ec2cae75c30e302bdefe256ccd5e25f59cf1dbfc Binary files /dev/null and b/original/G/T-REC-G.225-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.226-198811-I_PDF-E.pdf b/original/G/T-REC-G.226-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..75155adfd017e2ce574260692ef2a776f2dedb79 Binary files /dev/null and b/original/G/T-REC-G.226-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.230-198811-I_PDF-E.pdf b/original/G/T-REC-G.230-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..7be724a2da15bf7275001b6adb667fe809ad8498 Binary files /dev/null and b/original/G/T-REC-G.230-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.243-198811-I_PDF-E.pdf b/original/G/T-REC-G.243-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..2f62b162d90efca5da16486e3131a214ad452bb9 Binary files /dev/null and b/original/G/T-REC-G.243-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.325-198811-I_PDF-E.pdf b/original/G/T-REC-G.325-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..5ca44ec4026cff0caab47061388f84c2352fcb93 Binary files /dev/null and b/original/G/T-REC-G.325-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.343-198811-I_PDF-E.pdf b/original/G/T-REC-G.343-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..1f4e1a685e3ea98ac281c6738b909b208b482b52 Binary files /dev/null and b/original/G/T-REC-G.343-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.345-198811-I_PDF-E.pdf b/original/G/T-REC-G.345-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..e56fa350f3974cb104d97c718ceeb74666c79f48 Binary files /dev/null and b/original/G/T-REC-G.345-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.346-198811-I_PDF-E.pdf b/original/G/T-REC-G.346-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..0f0630aa7afe1ff72a6255c8b6a7ebe433262154 Binary files /dev/null and b/original/G/T-REC-G.346-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.411-198811-I_PDF-E.pdf b/original/G/T-REC-G.411-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..c1258dd1541d5962ff336354e6b73f32e5b64882 Binary files /dev/null and b/original/G/T-REC-G.411-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.421-198811-I_PDF-E.pdf b/original/G/T-REC-G.421-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..561642b397522099b77ded1827ecebf64df35a68 Binary files /dev/null and b/original/G/T-REC-G.421-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.422-198811-I_PDF-E.pdf b/original/G/T-REC-G.422-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..768fa770de4130068fd0a5f73c968d44a4d11c2e Binary files /dev/null and b/original/G/T-REC-G.422-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.431-198811-I_PDF-E.pdf b/original/G/T-REC-G.431-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..de3505a204bc0fb5a901ba7fb8a35efcc7db236a Binary files /dev/null and b/original/G/T-REC-G.431-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.441-198811-I_PDF-E.pdf b/original/G/T-REC-G.441-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..e5ff7b8fd2158072bfe8294eb7e5a9aa1611ff14 Binary files /dev/null and b/original/G/T-REC-G.441-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.442-198811-I_PDF-E.pdf b/original/G/T-REC-G.442-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..0046477d1d6ea2204732db8b6bb212d206f461be Binary files /dev/null and b/original/G/T-REC-G.442-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.451-198811-I_PDF-E.pdf b/original/G/T-REC-G.451-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..3f884a3e6a256aad3ed4a199b225be8cfe14c8f3 Binary files /dev/null and b/original/G/T-REC-G.451-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.613-198811-I_PDF-E.pdf b/original/G/T-REC-G.613-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..4f7228a99c2777bea85d43c15c80d8a184872055 Binary files /dev/null and b/original/G/T-REC-G.613-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.623-198811-I_PDF-E.pdf b/original/G/T-REC-G.623-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..3ce243cc5b072c14846a4c17903804a1eb8a1d70 Binary files /dev/null and b/original/G/T-REC-G.623-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.733-198811-I_PDF-E.pdf b/original/G/T-REC-G.733-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..023ed2d57302b9bf493a45468d06775d284f0f26 Binary files /dev/null and b/original/G/T-REC-G.733-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.736-199303-I_PDF-E.pdf b/original/G/T-REC-G.736-199303-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..28e7c7946d032198c2709b60177fc369df723893 Binary files /dev/null and b/original/G/T-REC-G.736-199303-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.743-198811-I_PDF-E.pdf b/original/G/T-REC-G.743-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..1dee91d5ebedee1498163bbb496af78ddd7dc11e Binary files /dev/null and b/original/G/T-REC-G.743-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.745-198811-I_PDF-E.pdf b/original/G/T-REC-G.745-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..daa491c1760c725b8cbb55af6a6f4acba88b9ba5 Binary files /dev/null and b/original/G/T-REC-G.745-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.746-198811-I_PDF-E.pdf b/original/G/T-REC-G.746-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..6e39b42cd707216ee9ff22aa8fc47ebf8e991054 Binary files /dev/null and b/original/G/T-REC-G.746-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.753-198811-I_PDF-E.pdf b/original/G/T-REC-G.753-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..9f6e190a4627728ea3d4d0c639120bddbe5c1e97 Binary files /dev/null and b/original/G/T-REC-G.753-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.755-198811-I_PDF-E.pdf b/original/G/T-REC-G.755-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..07a0bea65044e310e9f9a977b38442477b1aa9d1 Binary files /dev/null and b/original/G/T-REC-G.755-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.793-198811-I_PDF-E.pdf b/original/G/T-REC-G.793-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..17c431948e44ba9aa9cc4c3c749eeda78ae603dc Binary files /dev/null and b/original/G/T-REC-G.793-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.795-198811-I_PDF-E.pdf b/original/G/T-REC-G.795-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..4beafa63eccdba94aac8d9ffe47619b13b5df70f Binary files /dev/null and b/original/G/T-REC-G.795-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.852.12-199903-I_PDF-E.pdf b/original/G/T-REC-G.852.12-199903-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..bd2abebaceb5fadd5e6ee1ac504ff1a7dafd02ab Binary files /dev/null and b/original/G/T-REC-G.852.12-199903-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.852.3-199903-I_PDF-E.pdf b/original/G/T-REC-G.852.3-199903-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..2a08faa1dd7f543ebe9e0562936626038f2e8305 Binary files /dev/null and b/original/G/T-REC-G.852.3-199903-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.852.6-199903-I_PDF-E.pdf b/original/G/T-REC-G.852.6-199903-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..de6f861d89882f8b53d360b0f60ca11f6ae362cc Binary files /dev/null and b/original/G/T-REC-G.852.6-199903-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.852.8-199903-I_PDF-E.pdf b/original/G/T-REC-G.852.8-199903-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..7bab0dd8026d95d09d461b9d2cf21510c28f46ab Binary files /dev/null and b/original/G/T-REC-G.852.8-199903-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.853.10-199903-I_PDF-E.pdf b/original/G/T-REC-G.853.10-199903-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..33be972f31b40b05c8c458abd42cab87a15afe3a Binary files /dev/null and b/original/G/T-REC-G.853.10-199903-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.853.3-199903-I_PDF-E.pdf b/original/G/T-REC-G.853.3-199903-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..77d35e5bcd4c886a4708425cf5a62b559c28bed4 Binary files /dev/null and b/original/G/T-REC-G.853.3-199903-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.853.6-199903-I_PDF-E.pdf b/original/G/T-REC-G.853.6-199903-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..fac95b8e1bf979c1d0b0bfc9e3c8e94c597fb6ff Binary files /dev/null and b/original/G/T-REC-G.853.6-199903-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.853.8-199903-I_PDF-E.pdf b/original/G/T-REC-G.853.8-199903-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..ec0393d19b7c57093dd8924184a2753fcff2c7db Binary files /dev/null and b/original/G/T-REC-G.853.8-199903-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.854.12-199903-I_PDF-E.pdf b/original/G/T-REC-G.854.12-199903-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..2f062a0446166b9b02de178a114be60088ced8df Binary files /dev/null and b/original/G/T-REC-G.854.12-199903-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.950-198811-I_PDF-E.pdf b/original/G/T-REC-G.950-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..0cc005b838850c29907a1a30a90ff4350a099dda Binary files /dev/null and b/original/G/T-REC-G.950-198811-I_PDF-E.pdf differ diff --git a/original/G/T-REC-G.953-198811-I_PDF-E.pdf b/original/G/T-REC-G.953-198811-I_PDF-E.pdf new file mode 100644 index 0000000000000000000000000000000000000000..e06cd407ffd978c6543fd344c528d6755714d3fd Binary files /dev/null and b/original/G/T-REC-G.953-198811-I_PDF-E.pdf differ